Kashif Faraz 40d0dc9e0e Use separate executor to handle task updates in TaskQueue (#14533) ... Description: `TaskQueue.notifyStatus` is often a heavy call as it performs the following operations: - Update task status in metadata DB - Update task locks in metadata DB - Request (synchronously) the task runner to shutdown the completed task - Clean up in-memory data structures This method can often be slow and can cause worker sync / task runners to slow down. Main changes: - Run task completion callbacks in a separate executor to handle task completion updates - Add new config `druid.indexer.queue.taskCompleteHandlerNumThreads` - Add metrics to monitor number of processed and queued items - There are still other paths that can invoke `notifyStatus`, but those need not be moved to the new executor as they are synchronous on purpose. Other changes: - Add new metrics `task/status/queue/count`, `task/status/handled/count` - Add `TaskCountStatsProvider.getStats()` which deprecates the other `getXXXTaskCount` methods. - Use `CoordinatorRunStats` to collect and report metrics. This class has been used as is for now but will later be renamed and repurposed to use across all Druid services.		2023-07-07 20:43:12 +05:30
..
src	Use separate executor to handle task updates in TaskQueue (#14533)	2023-07-07 20:43:12 +05:30
pom.xml	Make LoggingEmitter more useful by using Markers (#14121)	2023-04-27 15:06:06 -07:00