[jira] [Updated] (IGNITE-12554) Ignite instance couldn't be restarted if it's parent thread group has been called destroy once

[ https://issues.apache.org/jira/browse/IGNITE-12554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Antonov updated IGNITE-12554: Description: I am using an inhouse platform which manage the life cycle of ignite

[jira] [Updated] (IGNITE-12554) Ignite instance couldn't be restarted if it's parent thread group has been called destroy once

[ https://issues.apache.org/jira/browse/IGNITE-12554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Antonov updated IGNITE-12554: Description: I am using an inhouse platform which manage the life cycle of ignite

[jira] [Created] (IGNITE-12554) Ignite instance couldn't be restarted if it's parent thread group has been called destroy once

ha faculty created IGNITE-12554: --- Summary: Ignite instance couldn't be restarted if it's parent thread group has been called destroy once Key: IGNITE-12554 URL: https://issues.apache.org/jira/browse/IGNITE-12554

[jira] [Updated] (IGNITE-11256) Implement read-only mode for grid

[ https://issues.apache.org/jira/browse/IGNITE-11256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Antonov updated IGNITE-11256: Fix Version/s: (was: 2.8) 2.9 > Implement read-only mode for grid

[jira] [Updated] (IGNITE-12554) Ignite instance couldn't be restarted if it's parent thread group has been called destroy once

[ https://issues.apache.org/jira/browse/IGNITE-12554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ha faculty updated IGNITE-12554: Description: I am using an inhouse platform which manage the life cycle of ignite instance by