[
https://issues.apache.org/jira/browse/IGNITE-21328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17809456#comment-17809456
]
Philipp Shergalis commented on IGNITE-21328:
--------------------------------------------
https://github.com/apache/ignite-3/pull/3073
> Fix logging in LowWatermark#start when there is no low watermark in vault
> -------------------------------------------------------------------------
>
> Key: IGNITE-21328
> URL: https://issues.apache.org/jira/browse/IGNITE-21328
> Project: Ignite
> Issue Type: Improvement
> Reporter: Kirill Tkalenko
> Assignee: Philipp Shergalis
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When starting a node, there is confusing logging at
> *org.apache.ignite.internal.table.distributed.LowWatermark#start* in the
> absence of a low watermark in the vault.
> Example message *Low watermark has been successfully got from the vault and
> is scheduled to be updated: null* it needs to be changed to something like
> "Previous value of the low watermark was not found, will schedule to update
> it".
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
