Details
-
Bug
-
Status: Resolved
-
Normal
-
Resolution: Fixed
-
None
-
Degradation - Resource Management
-
Normal
-
Normal
-
Adhoc Test
-
All
-
None
-
Description
Changes to streaming setup code for CASSANDRA-17663 mean that BulkLoader initializes the schema/system keyspace, which is not what we want in a tool. Initialization is due to a call to SystemKeyspace.getPreferredIP from the BulkLoader when it starts to transmit the SSTables from the bulk loader to the Cassandra instance.
getPreferredIP:1063, SystemKeyspace (org.apache.cassandra.db) sendMessage:213, StreamingMultiplexedChannel (org.apache.cassandra.streaming.async) sendControlMessage:191, StreamingMultiplexedChannel (org.apache.cassandra.streaming.async) sendControlMessage:1033, StreamSession (org.apache.cassandra.streaming) startStreamingFiles:1257, StreamSession (org.apache.cassandra.streaming) prepareSynAck:802, StreamSession (org.apache.cassandra.streaming) messageReceived:622, StreamSession (org.apache.cassandra.streaming) run:76, StreamDeserializingTask (org.apache.cassandra.streaming) run:30, FastThreadLocalRunnable (io.netty.util.concurrent) run:748, Thread (java.lang)
The existing BulkLoaderTest fails to detect this as it doesn't actually connect to anything so does not initialize streaming.
Affects 4.1 and trunk, and may affect 4.0, although the 4.0 patch for CASSANDRA-17663 is different than 4.1+, and may require different mitigation.
Attachments
Issue Links
- is caused by
-
CASSANDRA-17663 Ensure FileStreamTask cannot compromise shared channel proxy for system table when interrupted
- Resolved
- relates to
-
CASSANDRA-18370 BulkLoader tool initializes schema unnecessarily via streaming - 4.0
- Resolved