We should gracefully handle j.l.OutOfMemoryError exceptions in the NN or DN. We should catch them in a high-level handler, cleanly fail the RPC (vs sending back the OOM stackrace) or background thread, and shutdown the NN or DN. Currently the process is left in a not well-test tested state (continuously fails RPCs and internal threads, may or may not recover and doesn't shutdown gracefully).
|Field||Original Value||New Value|
|Assignee||Eli Collins [ eli2 ]|
|Target Version/s||0.23.1 [ 12318885 ]||2.0.0, 3.0.0 [ 12320353, 12320356 ]|
|Assignee||Eli Collins [ eli2 ]||Eli Collins [ eli ]|
|Assignee||Eli Collins [ eli ]|
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Resolution||Won't Fix [ 2 ]|