milenkovicm commented on PR #2462: URL: https://github.com/apache/datafusion-ballista/pull/2462#issuecomment-5718320108
the idea behind scheduler_id is to be able to link events with schedulers. for example if logs are shipped to a S3 bucket we can use scheduler id as part of the path. I don't believe scheduler_id needs to have some meaningful name. we can provide a scheduler configuration option to assign id to the executor, or if scheduler id is not configured a uuid can be generated (and printed to logs). this would cover both cases handling schedulers as pets or cattle scheduler id can also be part of `/api/state` so we can poll it from external process should we need scheduler id does it make any sense, wdyt ? -- 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]
