Anton Vinogradov created IGNITE-10497:
-----------------------------------------
Summary: jvm-pause-detector-worker should be JVM singleton
Key: IGNITE-10497
URL:
https://issues.apache.org/jira/browse/IGNITE-10497 Project: Ignite
Issue Type: Task
Reporter: Anton Vinogradov
Assignee: Dmitriy Sorokin
Debugging tests I see the following:
{noformat}
[2018-11-30 20:36:46,284][WARN ][jvm-pause-detector-worker][CacheConsistencyCheckOnReadTest9] Possible too long JVM pause: 5861 milliseconds.
[2018-11-30 20:36:46,287][WARN ][jvm-pause-detector-worker][CacheConsistencyCheckOnReadTest4] Possible too long JVM pause: 5863 milliseconds.
[2018-11-30 20:36:46,288][WARN ][jvm-pause-detector-worker][CacheConsistencyCheckOnReadTest3] Possible too long JVM pause: 5864 milliseconds.
[2018-11-30 20:36:46,288][WARN ][jvm-pause-detector-worker][CacheConsistencyCheckOnReadTest2] Possible too long JVM pause: 5864 milliseconds.
[2018-11-30 20:36:46,289][WARN ][jvm-pause-detector-worker][CacheConsistencyCheckOnReadTest1] Possible too long JVM pause: 5864 milliseconds.
[2018-11-30 20:36:46,290][WARN ][jvm-pause-detector-worker][CacheConsistencyCheckOnReadTest0] Possible too long JVM pause: 5865 milliseconds.
[2018-11-30 20:36:46,286][WARN ][jvm-pause-detector-worker][CacheConsistencyCheckOnReadTest6] Possible too long JVM pause: 5863 milliseconds.
[2018-11-30 20:36:46,286][WARN ][jvm-pause-detector-worker][CacheConsistencyCheckOnReadTest8] Possible too long JVM pause: 5863 milliseconds.
[2018-11-30 20:36:46,286][WARN ][jvm-pause-detector-worker][CacheConsistencyCheckOnReadTest5] Possible too long JVM pause: 5862 milliseconds.
{noformat}
Is there any reason to have more that one thread at one JVM?
Lest make jvm-pause-detector-worker static singleton.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
Locked
