Roman Puchkovskiy created IGNITE-17286:
------------------------------------------
Summary: Race between completing table creation and stopping
TableManager
Key: IGNITE-17286
URL: https://issues.apache.org/jira/browse/IGNITE-17286
Project: Ignite
Issue Type: Bug
Reporter: Roman Puchkovskiy
Fix For: 3.0.0-alpha6
As IGNITE-17048 demonstrates, our tests sometimes fail with message like the
following:
java.lang.AssertionError: Raft groups are still running
The leftover Raft groups always relate to table partitions (and NOT
metastorage/cmg).
It looks like this can happen due to TableManager.stop() being called before
some table creation is completed (on some Ignite node). As a result,
TableManager.stop() does not see this table, so the table does not get stopped,
and its Raft groups are left forever.
Adding a delay to table creation completion
public void onSqlSchemaReady(long causalityToken) {
if (Math.random() < 0.33) {
try {
Thread.sleep(1000);
} catch (InterruptedException e) {
// ignore
}
}
LOG.info("SCHEMA READY FOR " + causalityToken);
tablesByIdVv.complete(causalityToken);
}
makes the failure manifest itself easily.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
