Could not clear historyMap due to WAL reservation on cp

2020-12-02 Thread shivakumar
as there is continuous data ingestion. This is making WAL disk run out of space and pods crashes. when i see logs there are continuous warning messages saying Could not clear historyMap due to WAL reservation on cp: CheckpointEntry [id=e8bb9c22-0709-416f-88d6-16c5ca534024, timestamp=1606979158669

RE: Could not clear historyMap due to WAL reservation on cp

2020-12-06 Thread Alexandr Shapkin
WAL started growing linearly as there is continuousdata ingestion. This is making WAL disk run out of space and pods crashes. when i see logs there are continuous warning messages saying Could not clear historyMap due to WAL reservation on cp: CheckpointEntry[id=e8bb9c22-0709-416f-88d6-16c5ca534024

RE: Could not clear historyMap due to WAL reservation on cp

2020-12-07 Thread shivakumar
cleaned, Do you think there is something fixed in the above jira ticket related to my issue ? I tried collecting logs, the logs are very huge, i couldn't find any exceptions or error messages but I saw below warnings: "Partition states validation has failed for group" "Could not

RE: Could not clear historyMap due to WAL reservation on cp

2020-12-08 Thread shivakumar
-4c08-bc44-e08f191526d0, timestamp=1607438456546, ptr=WALPointer [idx=300, fileOff=148642467, len=10370]], history map size is 80"} {"type":"log","host":"ignite-cluster-ignite-shiva-0","level":"WARN","systemid":"039c963