[jira] [Updated] (IGNITE-9076) Service Grid: Introduce timeout to interrupt long Service#init on deployment
[ https://issues.apache.org/jira/browse/IGNITE-9076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Plekhanov updated IGNITE-9076: -- Fix Version/s: (was: 2.9) > Service Grid: Introduce timeout to interrupt long Service#init on deployment > > > Key: IGNITE-9076 > URL: https://issues.apache.org/jira/browse/IGNITE-9076 > Project: Ignite > Issue Type: Task > Components: managed services >Reporter: Vyacheslav Daradur >Assignee: Vyacheslav Daradur >Priority: Major > > According to the issue IGNITE-3392 we should propagate services deployment > results to an initiator, that means we should wait for Service#init method > completion. > We should introduce some kind of to interrupt long Service#init method on > deployment. > Probably it should be on per-service level. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-9076) Service Grid: Introduce timeout to interrupt long Service#init on deployment
[ https://issues.apache.org/jira/browse/IGNITE-9076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-9076: Fix Version/s: (was: 2.8) 2.9 > Service Grid: Introduce timeout to interrupt long Service#init on deployment > > > Key: IGNITE-9076 > URL: https://issues.apache.org/jira/browse/IGNITE-9076 > Project: Ignite > Issue Type: Task > Components: managed services >Reporter: Vyacheslav Daradur >Assignee: Vyacheslav Daradur >Priority: Major > Fix For: 2.9 > > > According to the issue IGNITE-3392 we should propagate services deployment > results to an initiator, that means we should wait for Service#init method > completion. > We should introduce some kind of to interrupt long Service#init method on > deployment. > Probably it should be on per-service level. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-9076) Service Grid: Introduce timeout to interrupt long Service#init on deployment
[ https://issues.apache.org/jira/browse/IGNITE-9076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-9076: Fix Version/s: (was: 2.7) 2.8 > Service Grid: Introduce timeout to interrupt long Service#init on deployment > > > Key: IGNITE-9076 > URL: https://issues.apache.org/jira/browse/IGNITE-9076 > Project: Ignite > Issue Type: Task > Components: managed services >Reporter: Vyacheslav Daradur >Assignee: Vyacheslav Daradur >Priority: Major > Fix For: 2.8 > > > According to the issue IGNITE-3392 we should propagate services deployment > results to an initiator, that means we should wait for Service#init method > completion. > We should introduce some kind of to interrupt long Service#init method on > deployment. > Probably it should be on per-service level. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9076) Service Grid: Introduce timeout to interrupt long Service#init on deployment
[ https://issues.apache.org/jira/browse/IGNITE-9076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Daradur updated IGNITE-9076: --- Description: According to the issue IGNITE-3392 we should propagate services deployment results to an initiator, that means we should wait for Service#init method completion. We should introduce some kind of to interrupt long Service#init method on deployment. Probably it should be on per-service level. was: According to the issue IGNITE-3392 we should propagate services deployment results to an initiator, that means we should wait for Service#init method completion. We should introduce some kind of timeout How should we handle Service#init method hangup? I propose to introduce some kind of IgniteSystemProperties#IGNITE_SERVICE_INIT_TIMEOUT to interrupt long initialization. > Service Grid: Introduce timeout to interrupt long Service#init on deployment > > > Key: IGNITE-9076 > URL: https://issues.apache.org/jira/browse/IGNITE-9076 > Project: Ignite > Issue Type: Task > Components: managed services >Reporter: Vyacheslav Daradur >Assignee: Vyacheslav Daradur >Priority: Major > Fix For: 2.7 > > > According to the issue IGNITE-3392 we should propagate services deployment > results to an initiator, that means we should wait for Service#init method > completion. > We should introduce some kind of to interrupt long Service#init method on > deployment. > Probably it should be on per-service level. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9076) Service Grid: Introduce timeout to interrupt long Service#init on deployment
[ https://issues.apache.org/jira/browse/IGNITE-9076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Daradur updated IGNITE-9076: --- Description: According to the issue IGNITE-3392 we should propagate services deployment results to an initiator, that means we should wait for Service#init method completion. We should introduce some kind of timeout How should we handle Service#init method hangup? I propose to introduce some kind of IgniteSystemProperties#IGNITE_SERVICE_INIT_TIMEOUT to interrupt long initialization. > Service Grid: Introduce timeout to interrupt long Service#init on deployment > > > Key: IGNITE-9076 > URL: https://issues.apache.org/jira/browse/IGNITE-9076 > Project: Ignite > Issue Type: Task > Components: managed services >Reporter: Vyacheslav Daradur >Assignee: Vyacheslav Daradur >Priority: Major > Fix For: 2.7 > > > According to the issue IGNITE-3392 we should propagate services deployment > results to an initiator, that means we should wait for Service#init method > completion. > We should introduce some kind of timeout > How should we handle Service#init method hangup? > I propose to introduce some kind of > IgniteSystemProperties#IGNITE_SERVICE_INIT_TIMEOUT to interrupt long > initialization. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
