kfaraz opened a new pull request, #18170:
URL: https://github.com/apache/druid/pull/18170
### Description
While working on #18147 , it became apparent that it would be nice to have
task logs for Indexer in separate files so that it is easier to debug them.
This can also come in handy while running Indexers in general.
This PR currently has two sets of changes:
- [Done] Route the logs from the main task thread to the task log file. This
is already working as verified through simulation tests by updating the
`log4j2.xml` in `extensions-core/multi-stage-query/src/main/resources` and
writing a simulation test in `quidem-ut`
- [WIP] Route the logs from other task threads (persist, push, publish) to
the same log file. This is currently a work in progress in this PR. It requires
some clean up of the appenderator API which is why all appenderator classes are
being moved to the `indexing-service` module.
<hr>
This PR has:
- [ ] been self-reviewed.
- [ ] using the [concurrency
checklist](https://github.com/apache/druid/blob/master/dev/code-review/concurrency.md)
(Remove this item if the PR doesn't have any relation to concurrency.)
- [ ] added documentation for new or modified features or behaviors.
- [ ] a release note entry in the PR description.
- [ ] added Javadocs for most classes and all non-trivial methods. Linked
related entities via Javadoc links.
- [ ] added or updated version, license, or notice information in
[licenses.yaml](https://github.com/apache/druid/blob/master/dev/license.md)
- [ ] added comments explaining the "why" and the intent of the code
wherever would not be obvious for an unfamiliar reader.
- [ ] added unit tests or modified existing tests to cover new code paths,
ensuring the threshold for [code
coverage](https://github.com/apache/druid/blob/master/dev/code-review/code-coverage.md)
is met.
- [ ] added integration tests.
- [ ] been tested in a test Druid cluster.
--
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]
