You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vyacheslav Daradur (JIRA)" <ji...@apache.org> on 2018/07/25 10:32:00 UTC
[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)