[
https://issues.apache.org/jira/browse/IGNITE-12714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17063396#comment-17063396
]
Anton Kalashnikov commented on IGNITE-12714:
--------------------------------------------
[~agura] yes, I think you are right about this. So I created a separate ticket
for that problem( https://issues.apache.org/jira/browse/IGNITE-12817) and
update the description for this ticket. But anyway I believe the current
changes still make sense because as I remember,
a separated default value for IGNITE_SYSTEM_WORKER_BLOCKED discussed on
dev-list the couple times.
> IGNITE_SYSTEM_WORKER_BLOCKED timeout is the same as FailureDetectionTimeout
> by default
> --------------------------------------------------------------------------------------
>
> Key: IGNITE-12714
> URL: https://issues.apache.org/jira/browse/IGNITE-12714
> Project: Ignite
> Issue Type: Bug
> Reporter: Anton Kalashnikov
> Assignee: Anton Kalashnikov
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Right now, the default value of sysWorkerBlockedTimeout is equal to
> FailureDetectionTimeout which is not ok because it is not the same thing. So
> it's needed to add a separate default value for sysWorkerBlockedTimeout
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
