ReadMeFeed / Community knowledge

#query-cancellation

Real questions. Useful conversations. Find the people who know your stack.

Question1 answer1,245 followingPosted 22 Oct 2024, 18:44 UTC55.6K views1,966 votes

Driver-enforced transaction timeout vs explicit cancel API: which provides predictable rollback semantics for long-running write transactions?

Goal Select a cancellation strategy for long-running Cypher write transactions that guarantees uncommitted changes are rolled back before any partial writes become visible, while avoiding the ambiguity where a cancellation error is returned even after a commit has succeeded. Constraints and uncertainty TransactionConfig.withTimeout(Duration) is enforced clie

Community & Careers · Editorial question

neo4j

Community & Careers

Question1 answer2,451 followingPosted 13 Dec 2023, 17:40 UTC96.1K views2,657 votes

owner answered

Context Deadline Exceeded Leaves Flux Query Running in InfluxDB OSS 2.x

When a client aborts an HTTP request to the InfluxDB query API before a Flux query completes, the response returns a context deadline exceeded error or a 504 Gateway Timeout, yet the query may keep running on the server. This behavior matters for long-running or high-cardinality queries where wasted CPU and memory accumulate. In InfluxDB OSS 2.x, the client

Community & Careers · Editorial question

query-cancellation http-api flux

Community & Careers

Question0 answers1,054 followingPosted 22 Jan 2022, 20:11 UTC100.1K views2,811 votes

Consistency of request cancellation states across database providers

Prisma Client allows for request cancellation by passing an AbortSignal via the AbortController API. This mechanism is intended to propagate the cancellation from the JavaScript layer to the Rust-based query engine to prevent resource leakage on the database server. While the client-side signal triggers the cancellation process, the actual behavior and repor

Community & Careers · Editorial question

prisma database-providers query-cancellation