t;
>
> --
> Jeff Jirsa
>
>
>> On Sep 20, 2017, at 5:38 AM, Corentin Chary wrote:
>>
>> Hello,
>> Looks like currently we don't automatically run any check when a new
>> pull request is created on github.
>>
>> It could be as simple as
>
ently it's already used
for some things.
Thoughs ?
--
Corentin Chary
http://xf.iksaif.net
-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org
ectively trigger trace or log for queries
>
> [2] https://issues.apache.org/jira/browse/CASSANDRA-11012 Allow tracing CQL
> of a
> specific client only, based on IP (range)
Not directly related, but to make (3) more useful it would also be
great to be able to list currently executing queries. I've had
multiple cases where read queries would just use all my slots and
never finish and it was quite painful to discover what the query was
exactly (slow query don't help if the query never finishes).
--
Corentin Chary
http://xf.iksaif.net
=15342248&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15342248
>
> On Thu, Dec 8, 2016 at 4:10 AM, Corentin Chary
> wrote:
>> Currently the StreamPlan created for bootstrap (and rebuild) will only
>> create one connection per host. If you
/commit/8352c21284811ca15d63183ceae0b11586623f31
would not work ?
I believe this is what is about
https://issues.apache.org/jira/browse/CASSANDRA-4663
See also: https://issues.apache.org/jira/browse/CASSANDRA-12229, but I
don't believe non-blocking I/O would change anything here.
--
Corentin
