Skip to content

Investigate: client session re-executed a completed query 90s later during enforce drill #1

Description

@sionsmith

During live enforce-suspend drill 4 (2026-06-12), the warmup query SELECT COUNT(*) ... WHERE amount > 8105 executed at 10:18:53 UTC (SUCCESS, result returned to client) and was re-executed at 10:20:23 UTC on the same Snowflake session (15548194833), resuming the warehouse chukei had suspended at 10:18:59.

Evidence rules out chukei's logged re-execution paths: zero cache hits (so no blame re-run), no retry-replay lines, no coalescing, and chukei has no upstream forward-retry. Suspects: snowflake-connector-python internal re-submission, or Snowflake-side query retry. The 90.0s delta matches the connector's default retry backoff pattern.

Impact if it's a client retry that chukei should have absorbed: the retry carried a requestId chukei's recent replay map should have served — check replay TTL vs 90s and whether the retry carried a fresh requestId.

Reproducer context: scripts/live-pilot.sh enforce drill; pilot-data/enforce4.log; QUERY_HISTORY session 15548194833.

🤖 Generated with Claude Code

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions