Hello project! Time (well, one day late. Sorry. =/) for our weekly check-in, and I'm up this week.
Link to JIRA board: https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=355&projectKey=CASSANDRA We've had 4 tickets open in the past week: https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=355&projectKey=CASSANDRA&quickFilter=1661&quickFilter=1670 . CASSANDRA-15613 and CASSANDRA-15614 are both flaky bootstrap test failures - these are probably good candidates to pick up if you're just getting started on the project and sampling things, or if you're perhaps more seasoned and just need a palate cleanser. We've closed out 11 tickets in the past week as well: https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=355&projectKey=CASSANDRA&quickFilter=1671 For a delta of -7 total tickets. Last week's query of total open scope was unfortunately missing FixVersion = 4.0-rc, so we see a total of 109 open tickets this week compared to the query of 93 last week. A more comparable indicator - the cumulative flow diagram continues to show healthy progress: https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=355&projectKey=CASSANDRA&view=reporting&chart=cumulativeFlowDiagram&swimlane=939&swimlane=936&swimlane=931&column=1505&column=1506&column=1514&column=1509&column=1512&column=1507&days=90 The creation of the testing sub-tasks on the 4.0 quality testing epic definitely bumped that graph, but I think it's good we now have one place to see some measure of the outstanding scope for the release. Testing Epic here: https://issues.apache.org/jira/browse/CASSANDRA-15536. There are still several tickets missing shepherds (assignees) and quite a few w/out "reviewers" (collaborators) so please poke around in there if you have an interest in helping test out subsystems for the 4.0 release. [Unassigned tickets] We have 5 alpha, 4 beta, and 16 RC tickets currently without assignees: https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=355&projectKey=CASSANDRA&view=detail&selectedIssue=CASSANDRA-15234&quickFilter=1658&quickFilter=1661 Some key tickets of interest: CASSANDRA-15306: Investigate why we are allocating 8MiB chunks and reaching the maximum BufferPool size https://issues.apache.org/jira/browse/CASSANDRA-15306 CASSANDRA-14801: calculatePendingRanges no longer safe for multiple adjacent range movements https://issues.apache.org/jira/browse/CASSANDRA-14801 CASSANDRA-15234: Standardise config and JVM parameters https://issues.apache.org/jira/browse/CASSANDRA-15234 David mentioned he might get to this one but in case anyone has cycles, probably straightforward enough Our current unassigned white whale from July of last year: CASSANDRA-15229: BufferPool Regression https://issues.apache.org/jira/browse/CASSANDRA-15229 The TL;DR from Benedict on the ticket: "The BufferPool was never intended to be used for a ChunkCache, and we need to either change our behaviour to handle uncorrelated lifetimes or use something else. " So this one could be quite an interesting challenge for someone that knows this portion of the codebase. [Stuck tickets - needs reviewer] https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=355&quickFilter=1661&quickFilter=1659 Cleaned up the JQL on this one - turns out we have 2 custom fields for both 'reviewer' and 'reviewers'. Thanks JIRA. 4 tickets in this bucket. Two that have languished a bit: CASSANDRA-14842: SSL connection problems when upgrading to 4.0 when upgrading from 3.0.x https://issues.apache.org/jira/browse/CASSANDRA-14842 CASSANDRA-14904: SSTableloader doesn't understand listening for CQL connections on multiple ports https://issues.apache.org/jira/browse/CASSANDRA-14904 [Notable tickets closed in the past week] CASSANDRA-15596 shows us that Brandon has officially lost his mind as he's working on Gossip tickets again. :) Documentation for virtual tables in CASSANDRA-15473 Improvement of token allocation when racks = RF in CASSANDRA-15600 Preview repair should include sstables from finalized incremental repair sessions in CASSANDRA-15553 And a variety of other good test fixes and stabilization. Thanks everyone for all the work on the project!
