[
https://issues.apache.org/jira/browse/IGNITE-13912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17269501#comment-17269501
]
shivakumar commented on IGNITE-13912:
-------------------------------------
Hi [[email protected]]
The last such message in [^server1-full-wal-checkpoint.log]
is
{code:java}
[2021-01-21T13:49:18,110][DEBUG][wal-file-cleaner%null-#82][FileWriteAheadLogManager]
Add current WAL archive size: -1073741408.0 B
[2021-01-21T13:49:18,110][DEBUG][wal-file-cleaner%null-#82][FileWriteAheadLogManager]
Last truncated WAL segment: 9{code}
But after that I see messages like this
{code:java}
[2021-01-21T13:53:39,924][DEBUG][wal-file-cleaner%null-#82][FileWriteAheadLogManager]
Available truncate WAL segments: 0{code}
As part of my testing I just connect/disconnect few times to visor to monitor
cache(last time also we observed this issue when we connect to visor). Apart
from this only one client program which ingest data (java program connects to
ignite over JDBC) is invoked in a loop.
My client program makes connection like this
// Open Connection to Ignite
System.out.println("Connecting to Ignite database...");
String url = IGNITE_DB_URL + ";" + IGNITE_DB_URL_PARAMETERS;
conn = DriverManager.getConnection(url, IGNITE_USER, IGNITE_PASS);
And ingest 10 million records and disconnect from database.
This connect–> ingest–>disconnect is in loop.
Not sure what is causing topology change but for sure there are no restarts of
server nodes.
> Incorrect calculation of WAL segments that should be deleted from WAL archive
> -----------------------------------------------------------------------------
>
> Key: IGNITE-13912
> URL: https://issues.apache.org/jira/browse/IGNITE-13912
> Project: Ignite
> Issue Type: Bug
> Components: persistence
> Reporter: Kirill Tkalenko
> Assignee: Kirill Tkalenko
> Priority: Critical
> Fix For: 2.10
>
> Attachments: server1-full-wal-checkpoint.log, wal-checkpoint-logs,
> wal_dir_contents, wal_grows_from_peak.PNG, wal_issue_reproduced.PNG,
> wal_usage.PNG, wal_usage_dec12.PNG, wal_usage_dec22nd_binary.PNG
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Now there is an incorrect calculation of WAL segments that should be deleted
> from WAL archive. Since we delete only those segments whose total size should
> not exceed *DataStorageConfiguration#maxWalArchiveSize *
> IGNITE_THRESHOLD_WAL_ARCHIVE_SIZE_PERCENTAGE*, but should be up to
> DataStorageConfiguration#maxWalArchiveSize *
> IGNITE_THRESHOLD_WAL_ARCHIVE_SIZE_PERCENTAGE*. Therefore, an excess of
> *DataStorageConfiguration#maxWalArchiveSize* occurs.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
