FYI, I raised Jira ticket https://issues.apache.org/jira/browse/IGNITE-20299
for this.
On Mon, Aug 28, 2023 at 3:42 PM Raymond Wilson
wrote:
> We have tried the same renaming in the dev environment which has multiple
> server nodes impacted and contains some data (unlike the local grid I
>
We have tried the same renaming in the dev environment which has multiple
server nodes impacted and contains some data (unlike the local grid I
tested this on which had a single server node containing no data). This
environment failed to restart after those changes.
We are still looking into it
Looking at the cache-SiteModelMetaData folder in the persistence folder for
a server node shows a "cache_data" file 6kb in size. No other cache folders
contain this file.
As an experiment I renamed this file to "cache_dataxxx". This appeared to
be sufficient to permit the grid to restart.
I have reproduced the possible bug I reported in my earlier email.
Given a running grid, having a client node in the grid attempt to create a
cache using a DataRegionName that does not exist in the grid causes
immediate failure in the client node with the following log output.
2023-08-27
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
