History Server

    Furthermore, it exposes a REST API that accepts HTTP requests and responds with JSON data.

    The HistoryServer allows you to query the status and statistics of completed jobs that have been archived by a JobManager.

    After you have configured the HistoryServer and JobManager, you start and stop the HistoryServer via its corresponding startup script:

    By default, this server binds to and listens at port 8082.

    The configuration keys jobmanager.archive.fs.dir and historyserver.archive.fs.refresh-interval need to be adjusted for archiving and displaying archived jobs.

    JobManager

    The archiving of completed jobs happens on the JobManager, which uploads the archived job information to a file system directory. You can configure the directory to archive completed jobs in flink-conf.yaml by setting a directory via jobmanager.archive.fs.dir.

    HistoryServer

    The contained archives are downloaded and cached in the local filesystem. The local directory for this is configured via historyserver.web.tmpdir.

    Check out the configuration page for a complete list of configuration options.

    Below is a list of available requests, with a sample JSON response. All requests are of the sample form , below we list only the path part of the URLs.

    Values in angle brackets are variables, for example http://hostname:port/jobs/<jobid>/exceptions will have to requested for example as http://hostname:port/jobs/7684be6004e4e955c2a558a9bc463f65/exceptions.

    • /config
    • /jobs/overview
    • /jobs/<jobid>/vertices
    • /jobs/<jobid>/config
    • /jobs/<jobid>/exceptions
    • /jobs/<jobid>/vertices/<vertexid>
    • /jobs/<jobid>/vertices/<vertexid>/taskmanagers
    • /jobs/<jobid>/vertices/<vertexid>/accumulators
    • /jobs/<jobid>/vertices/<vertexid>/subtasks/accumulators
    • /jobs/<jobid>/vertices/<vertexid>/subtasks/<subtasknum>
    • /jobs/<jobid>/vertices/<vertexid>/subtasks/<subtasknum>/attempts/<attempt>