[GitHub] [accumulo] ctubbsii opened a new issue #1435: Master OOME during GCUpgrade9to10TestIT (test fails)

[GitBox <gi...@apache.org>]

ctubbsii opened a new issue #1435: Master OOME during GCUpgrade9to10TestIT (test fails)
URL: https://github.com/apache/accumulo/issues/1435
 
 
   I am seeing repeated failures in GCUpgrade9to10TestIT ever since #1427 . It seems to be caused by the Master server getting an OutOfMemoryError, and the rest of the test waiting for it to come back before it times out. However, I cannot get a consistent stack trace in the logs from the master, to identify where in the code it is failing. I think it's in a child thread, because it keeps triggering the UncaughtExceptionHandler, and printing a basic message to the `.out` file that MiniAccumuloCluster creates, as in:
   
   ```
   Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread "Thread-2"
   ```
   
   The name of the thread is different each time, and it's unfortunate we don't have these threads named better. Jstack is no help, because the process is already dead by the time the I see the problem (which seems to happen quickly). Analyzing the relevant upgrade and test code seems to be the best chance to track this down.
   
   I've also seen this, but not every time:
   
   ```
   Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread "process reaper"
   OpenJDK 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGTERM to handler- the VM may need to be forcibly terminated
   ```
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services