Hearing no objections or concerns, I will begin the deprecation process[1]
for SystemFailure.
After that I'll remove the dependencies [2] on SystemFailure in the
membership subsystem.
[1] https://issues.apache.org/jira/browse/GEODE-7369
[2] https://issues.apache.org/jira/browse/GEODE-7354
The SystemFailure class is in the org.apache.geode package which means it
is part of the public API.
My purpose in messaging the dev list was to discover any concerns or
objections to adding the deprecated flag to SystemFailure per GEODE-7369.
Related to that work, I intend to eliminate calls to
Bill, are you proposing to remove calls to
SystemFailure.initiateFailure() and remove all of the emergency-class
stuff or just add a Deprecated flag to SystemFailure?
On 10/28/19 12:01 PM, Bill Burcham wrote:
The SystemFailure class is a clearing house for detecting and attempting to
mitigate
+1.
On Mon, Oct 28, 2019 at 4:22 PM Robert Houghton
wrote:
> +1.
>
> On Mon, Oct 28, 2019 at 12:11 PM Bill Burcham
> wrote:
>
> > The SystemFailure class is a clearing house for detecting and attempting
> to
> > mitigate SystemFailure exceptions e.g. VirtualMachineError and
> > OutOfMemoryError
+1.
On Mon, Oct 28, 2019 at 12:11 PM Bill Burcham
wrote:
> The SystemFailure class is a clearing house for detecting and attempting to
> mitigate SystemFailure exceptions e.g. VirtualMachineError and
> OutOfMemoryError.
>
> This class should not exist. SystemFailure exceptions should be allowed
The SystemFailure class is a clearing house for detecting and attempting to
mitigate SystemFailure exceptions e.g. VirtualMachineError and
OutOfMemoryError.
This class should not exist. SystemFailure exceptions should be allowed to
percolate up and cause the JVM to terminate as soon as possible wi
