KAFKA-14906:Extract the coordinator service log from server log #13568
Conversation
|
This would be a breaking change since users will have to change their operational scripts & runbooks to look for coordinator logs in a different file. Perhaps we should target this for 4.x? |
Do you mean that this change can be considered in the initial version of Kafka 4.x? |
|
I would suggest to mark the "fix version" of the JIRA as 4.0 and close this PR. It could be opened again when we start working on 4.0 as release target. There is currently no date decided in the community on when is that going to happen. |
OK, thx! |
|
Logging configuration is something the administrator can change as desired, right? Is there a clear benefit to the majority of users for this change? I can imagine it being a welcome change for some and an unexpected burden for others. Note: since I am not a Kafka administrator, feel free to ignore my comment 😉 |
|
This PR is being marked as stale since it has not had any activity in 90 days. If you would like to keep this PR alive, please ask a committer for review. If the PR has merge conflicts, please update it with the latest from trunk (or appropriate release branch) If this PR is no longer valid or desired, please feel free to close it. If no activity occurrs in the next 30 days, it will be automatically closed. |
Currently, the coordinator service log and server log are mixed together. When troubleshooting the coordinator problem, it is necessary to filter from the server log, which is not very convenient. Therefore, the coordinator log is separated like the controller log.