[
https://issues.apache.org/jira/browse/CASSANDRA-13403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16242078#comment-16242078
]
Ludovic Boutros commented on CASSANDRA-13403:
---------------------------------------------
Another thing in the logs :
{code}
INFO [CompactionExecutor:5] 2017-11-07 14:52:50,945
CompactionManager.java:1472 - Performing anticompaction on 2 sstables
INFO [CompactionExecutor:5] 2017-11-07 14:52:50,956
CompactionManager.java:1509 - Anticompacting
[BigTableReader(path='/data/cassandra/data/lubo_test/t_doc-64343790c31611e7a46403e2ed27ae86/mc-21-big-Data.db'),
BigTableReader(path='/data/cassandra/data/lubo_test/t_doc-64343790c31611e7a46403e2ed27ae86/mc-20-big-Data.db')]
INFO [CompactionExecutor:5] 2017-11-07 14:52:51,308
PerSSTableIndexWriter.java:279 - Scheduling index flush to
/data/cassandra/data/lubo_test/t_doc-64343790c31611e7a46403e2ed27ae86/mc-22-big-SI_i_doc.db
INFO [SASI-General:2] 2017-11-07 14:52:51,343 PerSSTableIndexWriter.java:330 -
Index flush to
/data/cassandra/data/lubo_test/t_doc-64343790c31611e7a46403e2ed27ae86/mc-22-big-SI_i_doc.db
took 34 ms.
{code}
{code}
INFO [CompactionExecutor:5] 2017-11-07 14:52:51,380 DataTracker.java:152 -
SSTableIndex.open(column: r, minTerm: 0, maxTerm: 0, minKey: 1, maxKey: 7,
sstable:
BigTableReader(path='/data/cassandra/data/lubo_test/t_doc-64343790c31611e7a46403e2ed27ae86/mc-22-big-Data.db'))
{code}
{code}
INFO [CompactionExecutor:5] 2017-11-07 14:52:51,381
PerSSTableIndexWriter.java:279 - Scheduling index flush to
/data/cassandra/data/lubo_test/t_doc-64343790c31611e7a46403e2ed27ae86/mc-23-big-SI_i_doc.db
INFO [SASI-General:2] 2017-11-07 14:52:51,412 PerSSTableIndexWriter.java:330 -
Index flush to
/data/cassandra/data/lubo_test/t_doc-64343790c31611e7a46403e2ed27ae86/mc-23-big-SI_i_doc.db
took 31 ms.
INFO [CompactionExecutor:5] 2017-11-07 14:52:51,413
CompactionManager.java:1488 - Anticompaction completed successfully,
anticompacted from 0 to 2 sstable(s).
INFO [CompactionExecutor:5] 2017-11-07 14:52:51,413 CompactionManager.java:694
- [repair #f1539d30-c3c2-11e7-8fe4-090a7aa7154d] Completed anticompaction
successfully
INFO [InternalResponseStage:14] 2017-11-07 14:52:51,782
RepairRunnable.java:340 - Repair command #1 finished in 1 second
{code}
The second index on the second SSTable does not seem to be opened/finished.
And the only known keys are between [1 to 7] which matches with the query
result:
{code:SQL}
cassandra@cqlsh> SELECT * from lubo_test.t_doc where r = 0;
id | r | cid
----+---+--------------------------------------
6 | 0 | 66f68be0-c316-11e7-a464-03e2ed27ae86
7 | 0 | 66f74f30-c316-11e7-a464-03e2ed27ae86
10 | 0 | 66faaa90-c316-11e7-a464-03e2ed27ae86
4 | 0 | 66f46900-c316-11e7-a464-03e2ed27ae86
3 | 0 | 66f37ea0-c316-11e7-a464-03e2ed27ae86
5 | 0 | 66f5a180-c316-11e7-a464-03e2ed27ae86
2 | 0 | 66f29440-c316-11e7-a464-03e2ed27ae86
1 | 0 | 66ea56e0-c316-11e7-a464-03e2ed27ae86
(8 rows)
{code}
> nodetool repair breaks SASI index
> ---------------------------------
>
> Key: CASSANDRA-13403
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13403
> Project: Cassandra
> Issue Type: Bug
> Components: sasi
> Environment: 3.10
> Reporter: Igor Novgorodov
> Assignee: Alex Petrov
> Attachments: 3_nodes_compaction.log, 4_nodes_compaction.log
>
>
> I've got table:
> {code}
> CREATE TABLE cservice.bulks_recipients (
> recipient text,
> bulk_id uuid,
> datetime_final timestamp,
> datetime_sent timestamp,
> request_id uuid,
> status int,
> PRIMARY KEY (recipient, bulk_id)
> ) WITH CLUSTERING ORDER BY (bulk_id ASC)
> AND bloom_filter_fp_chance = 0.01
> AND caching = {'keys': 'ALL', 'rows_per_partition': 'ALL'}
> AND comment = ''
> AND compaction = {'class':
> 'org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy',
> 'max_threshold': '32', 'min_threshold': '4'}
> AND compression = {'chunk_length_in_kb': '64', 'class':
> 'org.apache.cassandra.io.compress.LZ4Compressor'}
> AND crc_check_chance = 1.0
> AND dclocal_read_repair_chance = 0.1
> AND default_time_to_live = 0
> AND gc_grace_seconds = 864000
> AND max_index_interval = 2048
> AND memtable_flush_period_in_ms = 0
> AND min_index_interval = 128
> AND read_repair_chance = 0.0
> AND speculative_retry = '99PERCENTILE';
> CREATE CUSTOM INDEX bulk_recipients_bulk_id ON cservice.bulks_recipients
> (bulk_id) USING 'org.apache.cassandra.index.sasi.SASIIndex';
> {code}
> There are 11 rows in it:
> {code}
> > select * from bulks_recipients;
> ...
> (11 rows)
> {code}
> Let's query by index (all rows have the same *bulk_id*):
> {code}
> > select * from bulks_recipients where bulk_id =
> > baa94815-e276-4ca4-adda-5b9734e6c4a5;
> >
> ...
> (11 rows)
> {code}
> Ok, everything is fine.
> Now i'm doing *nodetool repair --partitioner-range --job-threads 4 --full* on
> each node in cluster sequentially.
> After it finished:
> {code}
> > select * from bulks_recipients where bulk_id =
> > baa94815-e276-4ca4-adda-5b9734e6c4a5;
> ...
> (2 rows)
> {code}
> Only two rows.
> While the rows are actually there:
> {code}
> > select * from bulks_recipients;
> ...
> (11 rows)
> {code}
> If i issue an incremental repair on a random node, i can get like 7 rows
> after index query.
> Dropping index and recreating it fixes the issue. Is it a bug or am i doing
> the repair the wrong way?
--
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
