Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 7 Oct 2016 01:12:20 +0000 (UTC)
From: "Jeremiah Jordan (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.13010251.1475781906000.759565.1475802740663@Atlassian.JIRA>
In-Reply-To: <JIRA.13010251.1475781906000@Atlassian.JIRA>
References: <JIRA.13010251.1475781906000@Atlassian.JIRA> <JIRA.13010251.1475781906350@arcas>
Subject: [jira] [Updated] (CASSANDRA-12754) Change
 cassandra.wait_for_tracing_events_timeout_secs default to -1 so C* doesn't
 wait on trace events to be written before responding to request by default
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 07 Oct 2016 01:12:22 -0000


     [ https://issues.apache.org/jira/browse/CASSANDRA-12754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jeremiah Jordan updated CASSANDRA-12754:
----------------------------------------
    Fix Version/s: 3.x
                   3.0.x
                   2.2.x

> Change cassandra.wait_for_tracing_events_timeout_secs default to -1 so C* doesn't wait on trace events to be written before responding to request by default
> ------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-12754
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12754
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Andy Tolbert
>            Assignee: Stefania
>             Fix For: 2.2.x, 3.0.x, 3.x
>
>
> [CASSANDRA-11465] introduces a new system property {{cassandra.wait_for_tracing_events_timeout_secs}} that controls whether or not C* waits for events to be written before responding to client.   The current default behavior is to wait up to 1 second and then respond and timeout.  
> If using probabilistic tracing this can cause queries to be randomly delayed up to 1 second.
> Changing the default to -1 (disabled and enabling it explicitly in {{cql_tracing_test.TestCqlTracing.tracing_unknown_impl_test}}.
> Ideally it would be nice to be able to control this behavior on a per request basis (which would require native protocol changes).


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)