vrajat opened a new pull request, #15303: URL: https://github.com/apache/pinot/pull/15303
This PR has a couple of minor cleanups of how Tracing methods are used. 1. Use `Tracing.ThreadAccountantOps.clear` 2. External modules do not need to create a `ThreadUsageProvider` For 1., the API usage was inconsistent. Context is setup using `Tracing.ThreadAccountantOps.setup[runner|worker]' but was cleared using `Tracing.getThreadAccountant().clear()`. Ideally external modules should not be calling `getThreadAccountant` to be consistent. However that proved to be too large a change. For 2., all calls to `Tracing.ThreadAccountantOps.setupWorker` were creating a `ThreadResourceUsageProvider` using the default contructor. Since no contextual information is required, this call has been moved into the function. Moreover, `setupRunner` call is also similar. -- 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: commits-unsubscr...@pinot.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@pinot.apache.org For additional commands, e-mail: commits-h...@pinot.apache.org
