-
Notifications
You must be signed in to change notification settings - Fork 13.3k
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
[FLINK-10123] Use ExecutorThreadFactory instead of DefaultThreadFactory in RestServer/Client #6539
Conversation
+1 |
Till, scala checkstyle error :
other travis build task also failed, because of some connection timeout. |
* limitations under the License. | ||
*/ | ||
|
||
package akka.actor |
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.
was this copied from akka?
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.
@zentol here we should use this package.
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.
We need to use the same package as the Akka classes since ActorSystemImpl
is package private private[akka]
. It is a bit ugly but it should work.
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.
+1 for bafd980
bafd980
to
c2f5429
Compare
checkstyle error :
|
c2f5429
to
74eadae
Compare
Thanks @yanghua. Fixed the PR. Let's see what Travis says this time :-) |
This closes apache#6339.
The RobustActorSystem has a configurable UncaughtExceptionHandler. Per default it is started with the FatalExitExceptionHandler. This handler terminates the JVM whenever it sees an uncaught exception. This closes apache#6334.
…ry in RestServer/Client Using the ExecutorThreadFactory hardens the system because it uses the FatalExitExceptionHandler as UncaughtExceptionHandler which terminates the JVM in case of an exception. This closes apache#6539.
74eadae
to
e307f92
Compare
What is the purpose of the change
Using the ExecutorThreadFactory hardens the system because it uses the FatalExitExceptionHandler
as UncaughtExceptionHandler which terminates the JVM in case of an exception.
Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:
@Public(Evolving)
: (no)Documentation