hello,
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;
normal.
then kill one node.
then execute SELECT COUNT(*) FROM city;
Failed to execute query because cache partition has been lostPart
[cacheName=City, part=0]
this alse normal.
Next, start the node that was shut down before.
then execute SELECT COUNT(*) FROM city;
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. Why still report this error? It is very confusing. Execute
reset_lost_partitions operation at this time seems redundant. Do have
any special considerations here?
if this time restart the whole cluster, thenexecute SELECT COUNT(*)
FROM city; normal, this state is the same as the previous state, but the
behavior is different.
