Details
Description
Start two nodes with native persistent enabled, and then activate it.
create a table with no backups, sql like follows:
CREATE TABLE City ( ID INT, Name VARCHAR, CountryCode CHAR(3), District VARCHAR, Population INT, PRIMARY KEY (ID, CountryCode) ) WITH "template=partitioned, affinityKey=CountryCode, CACHE_NAME=City, KEY_TYPE=demo.model.CityKey, VALUE_TYPE=demo.model.City"; INSERT INTO City(ID, Name, CountryCode, District, Population) VALUES (1,'Kabul','AFG','Kabol',1780000); INSERT INTO City(ID, Name, CountryCode, District, Population) VALUES (2,'Qandahar','AFG','Qandahar',237500);
then execute
SELECT COUNT FROM city;
The result is OK.
then kill one node and then execute
SELECT COUNT(*) FROM city;
The result is
Failed to execute query because cache partition has been lostPart [cacheName=City, part=0]
This is expected behavior as well.
Next, start the node that was shut down before and execute the same request:
SELECT COUNT(*) FROM city;
The result is the following:
Failed to execute query because cache partition has been lostPart [cacheName=City, part=0]
At this time, all partitions have been recovered, and all baseline nodes are ONLINE. Execute reset_lost_partitions operation at this time seems redundant.
Attachments
Issue Links
- incorporates
-
IGNITE-17657 Partition data loss after rolling restart
-
- Open
-