We believe we had some code on a dev environment attempt to create a cache that was intended for another Ignite.
The creation of this cache would have failed (at least) because the data region referenced in the cache configuration does not exist on that environment. A subsequent restart of the environment some time later started failing to initialise nodes on which the failed cache would have been stored had it succeeded. The failing nodes report this in the log: 2023-08-25 04:20:24,540 [44] WRN [ImmutableCacheComputeServer] Cache can not be started : cache=SiteModelMetadata 2023-08-25 04:20:11,265 [1] WRN [ImmutableCacheComputeServer] WAL segment tail reached. [idx=414, isWorkDir=true, serVer=org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordV2Serializer@c3719e5, actualFilePtr=WALPointer [idx=414, fileOff=452480679, len=0]] This error implies that (somehow) Ignite considers this to be a cache existing in the grid and is attempting to set it up. Raymond.
