[
https://issues.apache.org/jira/browse/CASSANDRA-9445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14587269#comment-14587269
]
Cheng Ren commented on CASSANDRA-9445:
--------------------------------------
Hi Philip,
Thanks so much for your reply.
Our schema of the table is:
CREATE TABLE br_product (
m_pid text,
b_paa blob,
b_page blob,
b_variant blob,
b_view_membership blob,
b_view_overrides blob,
c_canon_key text,
c_canon_url text,
c_url_flags text,
cat_crumbs map<text, text>,
cat_goog text,
cat_nodes map<text, text>,
d_age_group text,
d_brand text,
d_color_group map<text, text>,
d_colors map<text, text>,
d_conditions map<text, text>,
d_description text,
d_flags map<text, text>,
d_gender text,
d_keywords map<text, text>,
d_la_img_urls map<text, text>,
d_material map<text, text>,
d_mature boolean,
d_model_name text,
d_others map<text, text>,
d_pattern map<text, text>,
d_sizes map<text, text>,
d_stores map<text, text>,
d_sw_img_urls map<text, text>,
d_th_img_urls map<text, text>,
d_title text,
d_urls map<text, text>,
d_zo_img_urls map<text, text>,
i_buyable boolean,
i_have_avail boolean,
i_have_local_avail map<text, text>,
i_last_avail_ts timestamp,
i_level int,
i_price float,
i_price_rh float,
i_price_rl float,
i_price_tags map<text, text>,
i_sale_price float,
i_sale_price_rh float,
i_sale_price_rl float,
i_sale_price_tags map<text, text>,
i_status text,
is_blacklist boolean,
l_first_live_ts timestamp,
l_is_live boolean,
l_last_live_ts timestamp,
l_launch_ts timestamp,
pg_i_refs map<text, text>,
pg_o_refs map<text, text>,
pg_type text,
s_deleted int,
s_status_tags list<text>,
PRIMARY KEY (m_pid)
) WITH
bloom_filter_fp_chance=0.010000 AND
caching='KEYS_ONLY' AND
comment='' AND
dclocal_read_repair_chance=0.000000 AND
gc_grace_seconds=864000 AND
index_interval=128 AND
read_repair_chance=0.100000 AND
replicate_on_write='true' AND
populate_io_cache_on_flush='false' AND
default_time_to_live=0 AND
speculative_retry='99.0PERCENTILE' AND
memtable_flush_period_in_ms=0 AND
compaction={'class': 'SizeTieredCompactionStrategy'} AND
compression={'sstable_compression': 'LZ4Compressor'};
then we added a column as map<text,text>, dropped it and readded as blob.
We have backend and frontend dcs.
backend dc: We have pipelines running 2-4 times/day doing scan/write to
populate the table.
frontend dc: 20 lookups/second.
Please let me know if you need any more information.
Thanks
> 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)
