Re: JIRAs in Review
Hopefully it's not too late to add to this list.
https://issues.apache.org/jira/browse/CASSANDRA-14096 could use some
reviewing. This issue occurs if you have multiple tables in a keyspace
and perform a full repair. Then you could end up storing alot of
MerkleTrees in memory until the repair is completed.
The applied patch is for 3.0.x, but before creating patches for 4.0 I
thought it might be best to agree on the way forward (two solution
proposals have been provided).
On fre, 2018-07-20 at 15:42 +1000, kurt greaves wrote:
> Cheers Dinesh, not too worried about that one in 4.0's case though as
> a bug but it will need a committer.
> As for improvements for 4.0:
> https://issues.apache.org/jira/browse/CASSANDRA-13010 - More verbose
> nodetool compactionstats. Speaks for itself.
> https://issues.apache.org/jira/browse/CASSANDRA-10023 - Metrics for
> of local reads/writes. For detecting when you're choosing wrong
> coordinators. Useful for those of us without access to clients.
> https://issues.apache.org/jira/browse/CASSANDRA-10789 - nodetool
> command to stop bad clients. Would be great for the sysadmin toolbox.
> https://issues.apache.org/jira/browse/CASSANDRA-13841 - Smarter
> rebuild. Kind of a bug but would be nice to get it in 4.0 *at least*.
> probably need to rebase this)
> https://issues.apache.org/jira/browse/CASSANDRA-14309 - Hint window
> persistence. Would be nice to get some thoughts on this.
> https://issues.apache.org/jira/browse/CASSANDRA-12783 - Batchlog
> to better support MV's. Been meaning to get back to this one, but
> pretty much there except needs rebase and a bit more testing. Someone
> to go over it and see if it makes sense would be useful.
> May have traction? but worth keeping an eye on.
> https://issues.apache.org/jira/browse/CASSANDRA-14291 - Nodetool
> command to
> regenerate SSTable components. Mostly important for efficient
> summary/bloomfilter regeneration which doesn't exist apart from using
> upgradesstables. Other than that it's effectively upgradesstables but
> a cleaner interface. Chris has started looking at this but would
> be nice to make sure it gets in before 4.0 seeing as we have no way
> regenerate bloomfilter/summary without re-writing the entire SSTable
> Other than that hoping to get
> https://issues.apache.org/jira/browse/CASSANDRA-10540 (RangeAwareCS)
> in. On
> Markus' plate ATM but I'm fairly sure its been decently reviewed.
> On 19 July 2018 at 10:07, dinesh.joshi@xxxxxxxxx.INVALID <
> firstname.lastname@example.org> wrote:
> > Kurt was looking at some help with this ticket -
> > https://issues.apache.org/jira/browse/CASSANDRA-14525
> > Dinesh
> > On Tuesday, July 17, 2018, 12:35:25 PM PDT, sankalp kohli <
> > kohlisankalp@xxxxxxxxx> wrote:
> > Hi,
> > We are 7 weeks away from 4.0 freeze and there are ~150 JIRAs
> > waiting
> > for review. It is hard to know which ones should be prioritized as
> > some of
> > them could be not valid(fixes 2.0 bug), some of them will have the
> > assignee
> > who no longer is active, etc.
> > If anyone is *not* getting traction on the JIRA to get it reviewed,
> > please
> > use this thread to send your JIRA number and optionally why it is
> > important.
> > Thanks,
> > Sankalp
To unsubscribe, e-mail: dev-unsubscribe@xxxxxxxxxxxxxxxxxxxx
For additional commands, e-mail: dev-help@xxxxxxxxxxxxxxxxxxxx