Skip to content

Conversation

@iagaponenko
Copy link
Contributor

No description provided.

@iagaponenko iagaponenko force-pushed the tickets/DM-42005 branch 2 times, most recently from e90255c to ea7962d Compare February 6, 2025 09:12
@iagaponenko iagaponenko force-pushed the tickets/DM-42005 branch 4 times, most recently from 013e4f5 to 021a07a Compare February 13, 2025 04:33
@iagaponenko iagaponenko force-pushed the tickets/DM-42005 branch 2 times, most recently from c8f58ae to 9973d08 Compare March 3, 2025 20:57
@iagaponenko iagaponenko force-pushed the tickets/DM-42005 branch 4 times, most recently from cae38b9 to da02c98 Compare March 28, 2025 23:01
@iagaponenko iagaponenko force-pushed the tickets/DM-42005 branch 10 times, most recently from bf0a008 to 24c5495 Compare April 3, 2025 21:49
@iagaponenko iagaponenko force-pushed the tickets/DM-42005 branch 5 times, most recently from 154426a to 91c03f7 Compare April 14, 2025 21:23
@iagaponenko iagaponenko force-pushed the tickets/DM-42005 branch 2 times, most recently from b581b6a to 124acba Compare April 17, 2025 21:42
…uests

This function that was provisioned in the original design of the Replication
System has shown no benefits. Besides, the "duplicate" requests can't be
reliably detected since the detection algorithm is time dependent.
…service

Extended Replication Worker's config page on the Web Dashbnoard to display
connection parameters of the HTTP-based worker management services.
The new API allows embedding the partitioning tools into other
applications. Migrated error handling to throw exceptions instead of
calling std::exit(). Migrated the library code not to print anything
directly onto std::cout. Extended the ChunkIndex API to allow extracting
info on the resulting products of the translation.
@iagaponenko iagaponenko force-pushed the tickets/DM-42005 branch 9 times, most recently from 5e3245f to bfe655b Compare November 18, 2025 01:34
The new services extend chunk allocations (placement) to include all
existing replicas for the chunks in question instead of just one
allocation per chunk. The extended services are meant to be used by
the ingest workflows to push multiple replicas of a chunk in scenarios
where the replication level is bigger than 1 and multiple replicas
already exist in Qserv. The older services would fail in such scenarios.

Minor refactoring on the older code.

Fixed a bug in the JSON schema of  of the chunks allocation service
that was returning the key "location" instead of "locations". Migrated
the integration test accordingly.

Fixed a bug in the integration test.

Migratd the documentation on the Ingest API.
@iagaponenko iagaponenko force-pushed the tickets/DM-42005 branch 2 times, most recently from 5637d24 to 8d8afcd Compare November 18, 2025 21:57
Added a random delay in a range of 1 to 1001 milliseconds before
making transaction reatries after InnoDB deadlocks. The specific
problem to be addressed are inserts/deletions of rows into/from
a table with the AUTO_INCREMENT series.
Refactoring in the HTTP modules where it was needed to implement
the new feature and to prevent unnecessary code duplication.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants