[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: JIRAs in Review

Cheers Dinesh, not too worried about that one in 4.0's case though as it's
a bug but it will need a committer.

As for improvements for 4.0: - More verbose
nodetool compactionstats. Speaks for itself. - Metrics for number
of local reads/writes. For detecting when you're choosing wrong
coordinators. Useful for those of us without access to clients. - nodetool blacklist
command to stop bad clients. Would be great for the sysadmin toolbox. - Smarter nodetool
rebuild. Kind of a bug but would be nice to get it in 4.0 *at least*. (I
probably need to rebase this) - Hint window
persistence. Would be nice to get some thoughts on this. - Batchlog refactor
to better support MV's. Been meaning to get back to this one, but it's
pretty much there except needs rebase and a bit more testing. Someone else
to go over it and see if it makes sense would be useful.

May have traction? but worth keeping an eye on. - 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 with
a cleaner interface. Chris has started looking at this but would probably
be nice to make sure it gets in before 4.0 seeing as we have no way to
regenerate bloomfilter/summary without re-writing the entire SSTable ATM.

Other than that hoping to get (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 <
dinesh.joshi@xxxxxxxxx.invalid> wrote:

> Kurt was looking at some help with this ticket -
> 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