You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jim Witschey (JIRA)" <ji...@apache.org> on 2015/09/17 19:12:05 UTC
[jira] [Commented] (CASSANDRA-9445) Read timeout on the tables
where we recreated previously dropped column with different type
[ https://issues.apache.org/jira/browse/CASSANDRA-9445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14803242#comment-14803242 ]
Jim Witschey commented on CASSANDRA-9445:
-----------------------------------------
[~chengren311] I'm closing this for now, but please feel free to reopen it if you have more information.
> Read timeout on the tables where we recreated previously dropped column with different type
> -------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-9445
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9445
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Cheng Ren
>
> We had 10%~20% read request timeout on one specific table in our cassandra cluster.
> This happened since we added the column to that table with type of map<text,text>, ran the pipeline against it adding data and then dropped the column and re-added it as a blob with the same name. The pipeline run to populate the blob data happened as the problem began.
> The issue got fixed as soon as we dropped the column.
> Any clue why this is happening ? is there any similar issue been reported with this kind of column change?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)