cassandra-pr mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <>
Subject [GitHub] [cassandra] adelapena commented on a change in pull request #570: CASSANDRA-13606 Improve handling of 2i initialization failures
Date Mon, 18 May 2020 17:40:54 GMT

adelapena commented on a change in pull request #570:

File path: src/java/org/apache/cassandra/index/
@@ -655,6 +695,9 @@ private synchronized void markIndexFailed(Index index)
                 SystemKeyspace.setIndexRemoved(baseCfs.keyspace.getName(), indexName);
+            if (!index.getSupportedLoadTypeOnFailure().supportsWrites() && writableIndexes.remove(indexName)
!= null)
+      "Index [" + indexName + "] became not-writable.");

Review comment:
       Hi @bereng. I understand that the original behaviour was:
   return isInitialBuild ? LoadType.WRITE : LoadType.ALL;
   That's because the indexes were always writable independently of any kind of build failures,
there wasn't even a notion of writability. And, once they were queryable once, they were queryable
   Just took a quick look at the `SIMTest` failures, I think they are happening because `TestingIndex.shouldFailCreate`
is wrongly missed from `TestingIndex.clear()`. Once it's fixed to reset it, and we change
a couple of assertions about writability in `initializingIndexNotQueryableButWritableAfterPartialRebuild`,
all the tests seem to pass, at least locally.
   I'll take a closer look tomorrow.

This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message