[CASSANDRA-12755] Ability to control whether or not to wait on trace events being written before responding to client at request level

• Type: Improvement
• Status: Open
• Priority: Low
• Resolution: Unresolved
• Component/s: Legacy/CQL
• Assignee: Unassigned
• Reporter: Andy Tolbert
• Created: 06/Oct/16 19:30
• Updated: 16/Apr/19 09:30

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.

Instead it would be great if this could be configured on a per request basis (which would require a new flag at frame level or something else in protocol) and also as an option on the settraceprobability command.

Issue Links

• relates to: CASSANDRA-11465 dtest failure in cql_tracing_test.TestCqlTracing.tracing_unknown_impl_test
• relates to: 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