accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-4332) Tserver exiting due to uncaught error
Date Fri, 24 Jun 2016 00:20:16 GMT


Christopher Tubbs commented on ACCUMULO-4332:

I'm not sure there's a good sane way to handle an Error. I don't even think we should be trying
to catch them to do anything at all. We should just let the JVM die in case of Error.
I know we don't always follow this principle (we often try to catch "Throwable", which includes
Exception and Error). Maybe it makes sense to at least try to handle it, but in general, I
think it's better to just give up, because Errors are supposed to be JVM problems, not application

> Tserver exiting due to uncaught error
> -------------------------------------
>                 Key: ACCUMULO-4332
>                 URL:
>             Project: Accumulo
>          Issue Type: Bug
>    Affects Versions: 1.6.5
>            Reporter: Michael Wall
>             Fix For: 1.6.6, 1.7.3, 1.8.1
> After the following log statements, the tserver became a zombie and did nothing but spit
GC and Cache log statements.  The fix was to add more open files, ulimit -n was 1024.  This
ticket is to see if we can catch this exception and kill the tserver.
> {code}
> ERROR: run() exiting due to uncaught error
> java.lang.OutOfMemoryError: unable to create new native thread
>   at java.lang.Thread.start0(Native Method)
>   at java.lang.Thread.start(
>   at java.util.concurrent.ThreadPoolExecutor.addWorker(
>   at java.util.concurrent.ThreadPoolExecutor.execute(
>   at org.apache.thrift.server.THsHaServer.requestInvoke(
>   at org.apache.thrift.server.AbstractNonblockingServer$AbstractSelectThread.handleRead(
>   at org.apache.accumulo.server.util.CustomNonBlockerServer$
>   at org.apache.accumulo.server.util.CustomNonBlockerServer$
> {code}

This message was sent by Atlassian JIRA

View raw message