[GitHub] [accumulo] andrewglowacki edited a comment on issue #2331: OutOfMemoryError During BinMutations cause stuck BatchWriter

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

andrewglowacki edited a comment on issue #2331:
URL: https://github.com/apache/accumulo/issues/2331#issuecomment-956340936


   Yeah it's tricky. Unfortunately in this situation the error is recoverable and handling it is required in order to prevent resource leaks (stuck threads in this case).
   
   In either case, I think the system property is probably the easiest way to determine whether or not to halt. As far as notifying the user, I think the cleanest way is to use the existing mechanism (in 1.10.x) where the Throwable is re-thrown. Alternaively, it could be provided to a client side ucaught exception handler, but the BatchWriter/BatchScanner/etc would still have to be closed so the user thread is freed.


-- 
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.

To unsubscribe, e-mail: notifications-unsubscribe@accumulo.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org