Github user guoxiaolongzte commented on the issue:
https://github.com/apache/spark/pull/20259
Thank you for review, I will close this list. I'm going to use a script to
monitor the health of the Master process.
---
Github user jerryshao commented on the issue:
https://github.com/apache/spark/pull/20259
I kind of agree with @CodingCat , I think we have plenty of third-party
monitoring tools to monitor the availability of Master process, it is not so
necessary to expose here in Master UI.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/20259
Can one of the admins verify this patch?
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/20259
Can one of the admins verify this patch?
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
Github user guoxiaolongzte commented on the issue:
https://github.com/apache/spark/pull/20259
I set the startup time to a metric. The metric instead of the master page
display.
---
-
To unsubscribe, e-mail:
Github user guoxiaolongzte commented on the issue:
https://github.com/apache/spark/pull/20259
OK, i understand your suggestion.
Can I set the startup time to a metric?
---
-
To unsubscribe, e-mail:
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/20259
I don't think this number tells you the system is stable or not. If it did,
how is it actionable to users who don't have any access to investigate further?
Certainly, you should have proper
Github user guoxiaolongzte commented on the issue:
https://github.com/apache/spark/pull/20259
1. Concerned about the start-up time is to see if the system is stable.
2. Our system has 50,000 + app running every day, maser will generate a lot
of app registration, management
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/20259
I still don't understand why a user would care how long startup took. What
would they do with that? Admins and devs might. They should have access to
logs. The initial logs are available at startup
Github user guoxiaolongzte commented on the issue:
https://github.com/apache/spark/pull/20259
Sir, I stick to my point for the following reasons:
1.When the spark system is running for some time, the log has been rolled
back, because we use log4j, simply do not see the
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/20259
I don't think this is worth putting in the _UI_. It's already crowded. Log
it, sure.
---
-
To unsubscribe, e-mail:
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/20259
Can one of the admins verify this patch?
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
12 matches
Mail list logo
