-
Notifications
You must be signed in to change notification settings - Fork 218
feat: operator can be restarted #1675
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
closes #1578 |
@@ -376,6 +365,8 @@ public synchronized void stop() { | |||
|
|||
@Override | |||
public void start() throws OperatorException { | |||
// on restart new executor service is created and needs to be set here | |||
executor = ExecutorServiceManager.instance().executorService(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't the executor service be shut down then in stop
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes but what I meant is that we're lacking symmetry between start and stop here (i.e. the executor service is stopped at another level). Maybe stop
should set executor
to null
to prevent it from being used before being restarted? I guess this is more a theoretical question than a practical one.
Kudos, SonarCloud Quality Gate passed! |
@@ -376,6 +365,8 @@ public synchronized void stop() { | |||
|
|||
@Override | |||
public void start() throws OperatorException { | |||
// on restart new executor service is created and needs to be set here | |||
executor = ExecutorServiceManager.instance().executorService(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes but what I meant is that we're lacking symmetry between start and stop here (i.e. the executor service is stopped at another level). Maybe stop
should set executor
to null
to prevent it from being used before being restarted? I guess this is more a theoretical question than a practical one.
No description provided.