[
https://issues.apache.org/jira/browse/CASSANDRA-12244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16462348#comment-16462348
]
mck commented on CASSANDRA-12244:
---------------------------------
Looking green. Trunk's {{test-all}} is already broken, waiting on
CASSANDRA-14428.
And comparing failed dtests to their respective base branches:
- 3.0: stable {{bootstrap_test.TestBootstrap.test_simultaneous_bootstrap}}
failed, tested locally ok.
- 3.11: no difference.
- trunk: two additional failures:
{{bootstrap_test.TestBootstrap.test_decommissioned_wiped_node_can_join}} and
{{repair_tests.repair_test.TestRepair.test_dc_repair}}; neither are flakey but
both tested locally ok.
> progress in compactionstats is reported wrongly for view builds
> ---------------------------------------------------------------
>
> Key: CASSANDRA-12244
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12244
> Project: Cassandra
> Issue Type: Bug
> Reporter: Tom van der Woerdt
> Assignee: ZhaoYang
> Priority: Minor
> Labels: lhf
> Fix For: 3.0.x
>
>
> In the view build progress given by compactionstats, there are several issues
> :
> {code}
> id compaction type keyspace
> table completed total unit progress
> 038d3690-4dbe-11e6-b207-21ec388d48e6 View build mykeyspace
> mytable 844 bytes 967 bytes ranges 87.28%
> Active compaction remaining time : n/a
> {code}
> 1) those are ranges, not bytes
> 2) it's not at 87.28%, it's at ~4%. the method for calculating progress in
> Cassandra is wrong: it neglects to sort the tokens it's iterating through
> (ViewBuilder.java) and thus ends up with a random number.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
