[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

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 2.2.9, 3.0.10, 3.10
• Component/s: Legacy/Observability
• Severity: Normal
• Assignee: Stefania Alborghetti
• Reporter: Andy Tolbert

Authors

Stefania Alborghetti

Reviewers

Paulo Motta

• Created: 06/Oct/16 19:25
• Updated: 16/Apr/19 09:30
• Resolved: 25/Oct/16 01:49

Description

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).

Issue Links

• is related to: CASSANDRA-12755 Ability to control whether or not to wait on trace events being written before responding to client at request level
• relates to: CASSANDRA-11465 dtest failure in cql_tracing_test.TestCqlTracing.tracing_unknown_impl_test