Hello!
It might be safe to remove that file and restart node.
Regards,
--
Ilya Kasnacheev
вт, 4 дек. 2018 г. в 01:35, Raymond Wilson :
> Hi Ilya,
>
> I check the state of the WAL file in question (0008.wal) - it
> is a zero byte WAL file. The only other WAL file present in the
Hi Ilya,
I check the state of the WAL file in question (0008.wal) - it
is a zero byte WAL file. The only other WAL file present in the same
location is .wal (65536kb in size), which seems odd as
WALfiles 0001.wal through 0007.wal are not
Hello!
It seems that WAL file got truncated or something like that.
Can you post this file to some file storage so that we could look?
You can also try to change this node's WAL mode to LOG_ONLY and try to
start it again (after backing up data, of course). Checks are less strict
in this case.
Hi Ilya,
We don’t change the WAL segment size from the default values.
The only activity that occurred was stopping a node, making a minor change
(not related to persistence) and rerunning the node.
Raymond.
Sent from my iPhone
On 1/12/2018, at 2:52 AM, Ilya Kasnacheev wrote:
Hello!
"WAL
Hello!
"WAL segment size change is not supported"
Is there a chance that you have changed WAL segment size setting between
launches?
Regards,
--
Ilya Kasnacheev
чт, 29 нояб. 2018 г. в 02:39, Raymond Wilson :
> I'm using Ignite 2.6 with the C# client.
>
> I have a running cluster that I was
I'm using Ignite 2.6 with the C# client.
I have a running cluster that I was debugging. All requests were read only
(there were no state mutating operations running in the cluster.
I terminated the one server node in the grid (running in the debugger) to
make a small code change and re-run it (I
