[
https://issues.apache.org/jira/browse/IGNITE-26205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Puchkovskiy updated IGNITE-26205:
---------------------------------------
Description:
Default value for local config property
ignite.system.criticalWorkers.maxAllowedLagMillis has to be changed to 5000.
Properties that accompany this one (livenessCheckIntervalMillis and
nettyThreadsHeartbeatIntervalMillis) also need to be multiplied by 10.
Tests should still use the old defaults.
Motivation for changing the property value is that we often see complaints
about threads being 'blocked' for more than 500ms in the logs, even though the
node is still doing fine (even though experiences some short GC pauses)
was:
Default value for local config property
ignite.system.criticalWorkers.maxAllowedLagMillis has to be changed to 5000.
Properties that accompany this one (livenessCheckIntervalMillis and
nettyThreadsHeartbeatIntervalMillis) also need to be multiplied by 10.
Tests should still use the old defaults.
> Raise maxAllowedLagMillis default to 5 seconds
> ----------------------------------------------
>
> Key: IGNITE-26205
> URL: https://issues.apache.org/jira/browse/IGNITE-26205
> Project: Ignite
> Issue Type: Improvement
> Reporter: Roman Puchkovskiy
> Assignee: Roman Puchkovskiy
> Priority: Major
> Labels: ignite-3
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Default value for local config property
> ignite.system.criticalWorkers.maxAllowedLagMillis has to be changed to 5000.
> Properties that accompany this one (livenessCheckIntervalMillis and
> nettyThreadsHeartbeatIntervalMillis) also need to be multiplied by 10.
> Tests should still use the old defaults.
> Motivation for changing the property value is that we often see complaints
> about threads being 'blocked' for more than 500ms in the logs, even though
> the node is still doing fine (even though experiences some short GC pauses)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
