You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the AnomalyDetectorJobRunner, when the job runner's runJob() method is invoked by Job Scheduler, AD creates a Runnablehere that executes the job when invoked. The runnable is then submitted to this threadpool executor here for the threadpool named ad-threadpool.
The executor builder for this particular threadpool is instantiated here within the getExecutorBuilders extension point.
Within node.java, the executor builders for each plugin is retrieved here, which is then used to instantiate the threadpool here.
What solution would you like?
The SDK's BaseExtension interface should have a method called getExecutorBuilders in which we return a list of ExecutorBuilders from an extension. These executor builders should then be retrieved from the extension during ExtensionsRunner initialization and used to instantiate the threadpool here.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem?
In the
AnomalyDetectorJobRunner
, when the job runner'srunJob()
method is invoked by Job Scheduler, AD creates aRunnable
here that executes the job when invoked. The runnable is then submitted to this threadpool executor here for the threadpool namedad-threadpool
.The executor builder for this particular threadpool is instantiated here within the
getExecutorBuilders
extension point.Within node.java, the executor builders for each plugin is retrieved here, which is then used to instantiate the threadpool here.
What solution would you like?
The SDK's
BaseExtension
interface should have a method calledgetExecutorBuilders
in which we return a list of ExecutorBuilders from an extension. These executor builders should then be retrieved from the extension duringExtensionsRunner
initialization and used to instantiate the threadpool here.The text was updated successfully, but these errors were encountered: