streaming) can bring a huge single event log file which may cost a lot to maintain andĪlso requires a bunch of resource to replay per each update in Spark History Server.Įnabling and would Spark.history.* configuration options for the history server (default: none).Īpplying compaction on rolling event log filesĪ long-running application (e.g. May use the internal address of the server, resulting in broken links (default: none). If this is not set, links to application history ![]() The public address for the history server. JVM options for the history server (default: none).Ĭlasspath for the history server (default: none). Memory to allocate to the history server (default: 1g). The history server can be configured as follows: Environment Variables Environment Variable You can start the history server by executing: Provided that the application’s event logs exist. It is still possible to construct the UI of an application through Spark’s history server, This configures Spark to log Spark events that encode the information displayed To view the web UI after the fact, set to true before starting theĪpplication. Note that this information is only available for the duration of the application by default. If multiple SparkContexts are running on the same host, they will bind to successive ports You can access this interface by simply opening in a web browser.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |