ctubbsii edited a comment on issue #2331: URL: https://github.com/apache/accumulo/issues/2331#issuecomment-956549872
> libraries should not be shutting down the VM The library didn't cause the OutOfMemory (unless it did, in which case, the right solution is to fix our memory leakage! :smiley_cat:). The alternative is that the library intentionally leaves the client in a bad, likely unrecoverable, state. I'm not sure that's any better. This isn't that different from a segfault in a library that causes a process to die. Or, a memory-hogging native process to cause another process in the OS to be killed by the OOM-killer. No, a library shutting down the VM isn't good... but there aren't reliably good outcomes under Error conditions, by definition... that's why they are an Error instead of an Exception. > Edit - I see now, you said: > > > If there's a high demand or strong use case for it, I suppose I could support the idea of making the uncaught exception handler pluggable via client API. I'd support this approach. But, I have two standing concerns: 1. Enabling users to accidentally shoot themselves in the foot (and possibly "blame" Accumulo, because the errors appear to originate in Accumulo threads, and mishandling of the errors could lead to user code being affected), and 2. Increased code complexity to support this use case (that we might not even recommend users exercise). -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
