[GitHub] [hbase] Apache9 commented on pull request #2824: HBASE-25447 remoteProc is suspended due to OOM ERROR

2020-12-31 Thread GitBox
Apache9 commented on pull request #2824: URL: https://github.com/apache/hbase/pull/2824#issuecomment-752903200 > > > when throw "unable to create new native thread", the Thread does not run, jvm does not call uncaughtExceptionHandler > > > > > > I do not get your point here. The

[GitHub] [hbase] Apache9 commented on pull request #2824: HBASE-25447 remoteProc is suspended due to OOM ERROR

2020-12-31 Thread GitBox
Apache9 commented on pull request #2824: URL: https://github.com/apache/hbase/pull/2824#issuecomment-752894540 > when throw "unable to create new native thread", the Thread does not run, jvm does not call uncaughtExceptionHandler I do not get your point here. The current PR is to

[GitHub] [hbase] Apache9 commented on pull request #2824: HBASE-25447 remoteProc is suspended due to OOM ERROR

2020-12-30 Thread GitBox
Apache9 commented on pull request #2824: URL: https://github.com/apache/hbase/pull/2824#issuecomment-752825371 > if we don't have a better way to solve the issue or circumvent the issue, we can fix timeoutThread first, and at least the Proc is correct. OK. Then since TimeoutExecutor

[GitHub] [hbase] Apache9 commented on pull request #2824: HBASE-25447 remoteProc is suspended due to OOM ERROR

2020-12-29 Thread GitBox
Apache9 commented on pull request #2824: URL: https://github.com/apache/hbase/pull/2824#issuecomment-752316984 > > I guess the problem is that, since you set ulimit to a very low value, once there is no new thred allowed, the 'kill' command itself can not be executed either... > >

[GitHub] [hbase] Apache9 commented on pull request #2824: HBASE-25447 remoteProc is suspended due to OOM ERROR

2020-12-29 Thread GitBox
Apache9 commented on pull request #2824: URL: https://github.com/apache/hbase/pull/2824#issuecomment-752314818 Could you please try other options to see if it works? This is an automated message from the Apache Git Service.

[GitHub] [hbase] Apache9 commented on pull request #2824: HBASE-25447 remoteProc is suspended due to OOM ERROR

2020-12-29 Thread GitBox
Apache9 commented on pull request #2824: URL: https://github.com/apache/hbase/pull/2824#issuecomment-752313702 https://www.codementor.io/@suryab/outofmemoryerror-related-jvm-arguments-w6e4vgipt This is an automated message

[GitHub] [hbase] Apache9 commented on pull request #2824: HBASE-25447 remoteProc is suspended due to OOM ERROR

2020-12-29 Thread GitBox
Apache9 commented on pull request #2824: URL: https://github.com/apache/hbase/pull/2824#issuecomment-752313202 I guess the problem is that, since you set ulimit to a very low value, once there is no new thred allowed, the 'kill' command itself can not be executed either...

[GitHub] [hbase] Apache9 commented on pull request #2824: HBASE-25447 remoteProc is suspended due to OOM ERROR

2020-12-29 Thread GitBox
Apache9 commented on pull request #2824: URL: https://github.com/apache/hbase/pull/2824#issuecomment-752312107 So the problem is OnOutOfMemoryError flag does not work for "Unable to create new native thread"? This is an

[GitHub] [hbase] Apache9 commented on pull request #2824: HBASE-25447 remoteProc is suspended due to OOM ERROR

2020-12-29 Thread GitBox
Apache9 commented on pull request #2824: URL: https://github.com/apache/hbase/pull/2824#issuecomment-752297484 > > In general, if there is an OOME, we can not assume that our handler can still be executed correctly, as we do not know where is the OOME thrown out, it may break the

[GitHub] [hbase] Apache9 commented on pull request #2824: HBASE-25447 remoteProc is suspended due to OOM ERROR

2020-12-29 Thread GitBox
Apache9 commented on pull request #2824: URL: https://github.com/apache/hbase/pull/2824#issuecomment-752115741 Have we observed errors other than OOME which cause the TimeoutExecutorThread to hang there? This is an

[GitHub] [hbase] Apache9 commented on pull request #2824: HBASE-25447 remoteProc is suspended due to OOM ERROR

2020-12-29 Thread GitBox
Apache9 commented on pull request #2824: URL: https://github.com/apache/hbase/pull/2824#issuecomment-751997962 In general, if there is an OOME, we can not assume that our handler can still be executed correctly, as we do not know where is the OOME thrown out, it may break the assumptions