FrankChen021 commented on pull request #10418: URL: https://github.com/apache/druid/pull/10418#issuecomment-698060829
Hi @vogievetsky What you suggestion depends on how we define `tier`. The initial `tier` comes from historical nodes that serve different data retention rules. From the user's view on all druid nodes, I think `tier` could also used to describe different `roles` of nodes with same node type, which means for coordinators, the division of leader and non-leader also fit into this definition. And for the back-end implementation, this PR chooses to put the information in `tier` field for simplicity. BTW, I'll check and fix the integration tests failure later. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
