[
https://issues.apache.org/jira/browse/CASSANDRA-13712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16136889#comment-16136889
]
Aleksey Yeschenko commented on CASSANDRA-13712:
-----------------------------------------------
Schema propagation is not instantaneous, and even it were, there'd still
possibly be encoded hints in the write buffers. This is not an issue, because
they'll be safely skipped on replay.
> DropTable could cause hints
> ---------------------------
>
> Key: CASSANDRA-13712
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13712
> Project: Cassandra
> Issue Type: Bug
> Components: Coordination
> Reporter: Jay Zhuang
> Priority: Minor
>
> While dropping table and there's on going write traffic, we saw hints
> generated on each node. You can find hints dispatch message in the log. Not
> sure if it's an issue.
> Here are the reproduce steps:
> 1. Create a 3 nodes cluster:
> {{$ ccm create test13696 -v 3.0.14 && ccm populate -n 3 && ccm start}}
> 2. Send some traffics with cassandra-stress (blogpost.yaml is only in trunk,
> if you use another yaml file, change the RF=3)
> {{$ tools/bin/cassandra-stress user profile=test/resources/blogpost.yaml
> cl=QUORUM truncate=never ops\(insert=1\) duration=30m -rate threads=2 -mode
> native cql3 -node 127.0.0.1}}
> 3. While the traffic is running, drop table
> {{$ cqlsh -e "drop table stresscql.blogposts"}}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
