gaborgsomogyi edited a comment on pull request #33917: URL: https://github.com/apache/spark/pull/33917#issuecomment-914331337
1. If history server is down then restart is needed. It can be started on another machine but it's absolutely not must. 2. If multiple history servers are running then they need different config because they handle different clusters, right? If 2 history servers are sitting in the same directory then they corrupt the data inside. A good example is when HS does compaction in streaming use-cases. > Also hiveserver2 ,LivyServer use same patter Well, somebody already added this pattern but this doesn't convince me that the codebase need to be increased. If less configuration is super important it's possible to create headless keytabs w/o any code change. The effect would be the same... ``` Headless keytab What you call 'headless keytab' is user principal keys. This already makes an assumption that you have a user principal that corresponds to certain POSIX user it will start services without prompting for password e.g(smokeuser,hdfs,hbase). Headless principals are not bound to a specific host or node, they have the syntax: - @ EXAMPLE.COM For Example: Headless: [email protected] ``` All in all knowing these I'm not against to add it but I personally not intended to merge it. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
