Pin CnosDB CI to community-2026-02-16#1341
Closed
mrigger wants to merge 5 commits into
Closed
Conversation
CnosDB community-latest builds since 2026-02-17 regress with "Tskv: Index: index storage error: Resource temporarily unavailable (os error 11)" on DROP DATABASE, causing TestCnosDBNoREC to fail with expected: <0> but was: <-1>. Local bisect across the rolling community tags identifies 2026-02-16 as the last reliably passing build. The community-* tags are daily snapshots; CnosDB has no LTS/release tag, so pin to a known-good date until upstream stabilizes. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This reverts commit 75931d2.
Pinning the CnosDB image alone did not fix CI: 16 concurrent worker
threads hammering CREATE/DROP DATABASE overload CnosDB's Tskv index
storage with EAGAIN ("Resource temporarily unavailable (os error 11)")
regardless of the image version. Locally the default config fails
reproducibly with hundreds of these errors, while --num-threads 1
--num-tries 5 completes cleanly in ~3 min on community-latest.
The tests already disable query execution (--num-queries 0) since the
existing CnosDB integration is known to crash the database; reducing
the iteration count is consistent with that intent.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
CnosDB's HTTP listener starts almost immediately, but its Tskv storage layer takes additional seconds to initialize; running the first DROP DATABASE before it is ready returns EAGAIN. The previous probe (nc -z on the port) only confirms TCP, not DDL readiness. Poll a probe DROP+CREATE round-trip until it succeeds before handing off to mvn. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
cnosdb/cnosdb:community-* returns EAGAIN ("Tskv: Index: index storage
error: Resource temporarily unavailable (os error 11)") on DROP
DATABASE shortly after start. Even with --num-threads 1 --num-tries 5
and a SQL/DDL readiness probe (which itself completes in 2s), a real
DROP issued ~30s later still fails. The instability is server-side and
client retries cannot outrun it; CnosDB ships no LTS tag to pin to.
The job has been red on main for 14+ months.
Skip the job (if: false) rather than delete it so it can be re-enabled
once upstream stabilizes. Also drop the now-useless readiness probe.
Reported upstream: cnosdb/cnosdb#2435
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
72389a2 to
38350f3
Compare
Merged
Contributor
Author
|
Closed due to #1342. |
duerwuyi
pushed a commit
to duerwuyi/sqlancer
that referenced
this pull request
Apr 27, 2026
CnosDB returns EAGAIN ("Tskv: Index: index storage error: Resource
temporarily unavailable (os error 11)") on DROP DATABASE under
SQLancer's DDL load (cnosdb/cnosdb#2435). The CI job has been red on
main for 14+ months, the only published image tags are rolling daily
builds (no LTS), and upstream development appears stalled. Pin and
retry attempts (sqlancer#1341) did not help.
Remove the CnosDB provider, tests, CI job, and documentation entries.
Move CnosDB to the "Previously Supported DBMS" table in CONTRIBUTING.md.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
CnosDB community-latest builds since 2026-02-17 regress with "Tskv: Index: index storage error: Resource temporarily unavailable (os error 11)" on DROP DATABASE, causing TestCnosDBNoREC to fail with expected: <0> but was: <-1>. Local bisect across the rolling community tags identifies 2026-02-16 as the last reliably passing build.
The community-* tags are daily snapshots; CnosDB has no LTS/release tag, so pin to a known-good date until upstream stabilizes.