[CASSANDRA-14168] Throw error when attempting to mutate non-existant table

• Type: Bug
• Status: Open
• Priority: Normal
• Resolution: Unresolved
• Component/s: Legacy/Core, Legacy/Distributed Metadata
• Severity: Normal
• Assignee: Paulo Motta
• Reporter: Paulo Motta

Authors

Paulo Motta

• Created: 15/Jan/18 20:16
• Updated: 02/Oct/20 15:15

Description

When a node receives a write request for a table that was just created but it's TableMetadata is not yet registered, it will throw a UnknownTableException.

There is a small racy period though between when the TableMetadata is registered and it's ColumnFamilyStore is created, that a write request can be silently dropped due to ColumnFamilyStore not being instantiated - even though an error is logged, the request will be completed and an ack wrongly sent to the coordinator.

This was detected during investigation of a flakiness on materialized_views_test.py:TestMaterializedViews.populate_mv_after_insert_wide_rows_test.

ps: this is not an issue before 4.0, because a new table's TableMetadata was only registered after its
ColumnFamilyStore object was loaded (which appears to be changed by CASSANDRA-9425).

Issue Links

• is a child of: CASSANDRA-15921 4.0 quality testing: Materialized View