[
https://issues.apache.org/jira/browse/CASSANDRA-13738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16150783#comment-16150783
]
Jay Zhuang commented on CASSANDRA-13738:
----------------------------------------
2.2 branch uTest fail for {{ant eclipse-warnings}}, but I'm unable to reproduce
it locally:
{noformat}
eclipse-warnings:
[mkdir] Created dir: /home/ubuntu/cassandra/build/ecj
[echo] Running Eclipse Code Analysis. Output logged to
/home/ubuntu/cassandra/build/ecj/eclipse_compiler_checks.txt
[java] incorrect classpath: /home/ubuntu/cassandra/build/cobertura/classes
[java] ----------
[java] 1. ERROR in
/home/ubuntu/cassandra/src/java/org/apache/cassandra/db/compaction/CompactionManager.java
(at line 853)
[java] ISSTableScanner scanner = cleanupStrategy.getScanner(sstable,
getRateLimiter());
[java] ^^^^^^^
[java] Resource 'scanner' should be managed by try-with-resource
[java] ----------
[java] ----------
[java] 2. ERROR in
/home/ubuntu/cassandra/src/java/org/apache/cassandra/db/compaction/LeveledCompactionStrategy.java
(at line 257)
[java] scanners.add(new LeveledScanner(intersecting, range));
[java] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[java] Potential resource leak: '<unassigned Closeable value>' may not be
closed
[java] ----------
[java] ----------
[java] 3. ERROR in
/home/ubuntu/cassandra/src/java/org/apache/cassandra/tools/SSTableExport.java
(at line 315)
[java] ISSTableScanner scanner = reader.getScanner();
[java] ^^^^^^^
[java] Resource 'scanner' should be managed by try-with-resource
[java] ----------
[java] 3 problems (3 errors)
{noformat}
And for the other test failures, I don't think they're introduced by this patch.
> Load is over calculated after each IndexSummaryRedistribution
> -------------------------------------------------------------
>
> Key: CASSANDRA-13738
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13738
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Jay Zhuang
> Assignee: Jay Zhuang
> Fix For: 2.2.x, 3.0.x, 3.11.x, 4.x
>
> Attachments: sizeIssue.png
>
>
> For example, here is one of our cluster with about 500GB per node, but
> {{nodetool status}} shows far more load than it actually is and keeps
> increasing, restarting the process will reset the load, but keeps increasing
> afterwards:
> {noformat}
> Status=Up/Down
> |/ State=Normal/Leaving/Joining/Moving
> -- Address Load Tokens Owns (effective) Host ID
> Rack
> UN IP1***** 13.52 TB 256 100.0%
> c4c31e0a-3f01-49f7-8a22-33043737975d rac1
> UN IP2***** 14.25 TB 256 100.0%
> efec4980-ec9e-4424-8a21-ce7ddaf80aa0 rac1
> UN IP3***** 13.52 TB 256 100.0%
> 7dbcfdfc-9c07-4b1a-a4b9-970b715ebed8 rac1
> UN IP4***** 22.13 TB 256 100.0%
> 8879e6c4-93e3-4cc5-b957-f999c6b9b563 rac1
> UN IP5***** 18.02 TB 256 100.0%
> 4a1eaf22-4a83-4736-9e1c-12f898d685fa rac1
> UN IP6***** 11.68 TB 256 100.0%
> d633c591-28af-42cc-bc5e-47d1c8bcf50f rac1
> {noformat}
> !sizeIssue.png|test!
> The root cause is if the SSTable index summary is redistributed (typically
> executes hourly), the updated SSTable size is added again.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
