[
https://issues.apache.org/jira/browse/IGNITE-21509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Puchkovskiy updated IGNITE-21509:
---------------------------------------
Summary: Make MaxClockSkew configurable (was: Move MaxClockSkew to the
cluster configuration)
> Make MaxClockSkew configurable
> ------------------------------
>
> Key: IGNITE-21509
> URL: https://issues.apache.org/jira/browse/IGNITE-21509
> Project: Ignite
> Issue Type: Improvement
> Reporter: Roman Puchkovskiy
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> Currently, MaxClockSkew is hardcoded in HybridTimestamp. It should be
> configurable by the user, so we need to create a distributed cluster
> configuration entry for it.
> It needs to be immutable (at least for now, for simplicity); also, its value
> must not exceed delayDuration (optimally, MaxClockSkew should be less than
> delayDuration, maybe half of it or smaller).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
