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

Re: JIRAs in Review

We have a few improvements and bug fixes that could use reviewer feedback.

Useful improvements for 4.0: and - Makes the user
interface for creating keyspaces easier to use and less error prone. For
example "CREATE KEYSPACE foo WITH replication = {'class':
'NetworkTopologyStrategy'}" would just do the right thing after both
patches. - Limits the
DynamicEndpointSnitch's use of latent replicas. This should help with slow
queries on startup and every 10 minutes during DES reset (when the snitch's
latency data is empty). There is also a riskier potential follow up patch
which improves the performance of the latency tracking mechanism by ~10x
and reduces garbage to near zero. I believe that Jason is looking at this. - Improves the
startup check functionality to make it so that operators can be more
confident that they won't throw unavailable or timeouts during node
restarts. The patch has merge conflicts right now but I was waiting on
someone to confirm it's worth doing before I spend more time on it.

In progress patches for 4.0 that will probably need reviewers soon: - Improves the
handling of network partitions, especially those caused by statefull
firewalls (e.g. AWS security groups) - Initial sidecar and
distributed scheduler for repair. We're working on this port more or less
fulltime to try to get a patch before August 1st so someone can review.

Minor cleanup patches: - Cleanup of some old
configuration, probably an easy thing to commit.

Unrelated to this, how do I get the ability to assign myself to issues?
Right now someone else has to assign me/sumanth whenever we work on a
ticket and that's slightly odd.

Thanks Sankalp for sending this request out!

On Tue, Jul 17, 2018 at 12:35 PM sankalp kohli <kohlisankalp@xxxxxxxxx>

> 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

( ! ) Warning: include(msgfooter.php): failed to open stream: No such file or directory in /var/www/git/apache-cassandra-development/msg02379.html on line 128
Call Stack
10.0006368744{main}( ).../msg02379.html:0

( ! ) Warning: include(): Failed opening 'msgfooter.php' for inclusion (include_path='.:/var/www/git') in /var/www/git/apache-cassandra-development/msg02379.html on line 128
Call Stack
10.0006368744{main}( ).../msg02379.html:0