Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(ilp): commit pending rows after a timeout if no further ingestion #1731

Merged
merged 13 commits into from
Jan 13, 2022

Conversation

glasstiger
Copy link
Contributor

@glasstiger glasstiger commented Dec 23, 2021

While ingesting data via ILP there is a commit after a certain number of rows (cairo.max.uncommitted.rows) are inserted into a table.
However, it is likely that there will be a number of rows waiting for commit after ingestion stopped.
A maintenance job runs which will eventually commit these rows.
This job is usually configured to run infrequently (line.tcp.maintenance.job.interval) so it can take some time while the data appears in the database.
This PR will introduce a new config parameter (line.tcp.commit.timeout) which should be set to a much lower number.
If ingestion stops and the table has been idle for the time set in this new config parameter a commit will be issued automatically.

@glasstiger glasstiger marked this pull request as ready for review January 13, 2022 18:20
@ideoma
Copy link
Collaborator

ideoma commented Jan 13, 2022

[PR Coverage check]

😍 pass : 27 / 32 (84.38%)

file detail

path covered line new line coverage
🔵 io/questdb/cutlass/line/tcp/TableUpdateDetails.java 14 19 73.68%
🔵 io/questdb/PropServerConfiguration.java 1 1 100.00%
🔵 io/questdb/cutlass/line/tcp/LineTcpMeasurementScheduler.java 1 1 100.00%
🔵 io/questdb/cutlass/line/tcp/DefaultLineTcpReceiverConfiguration.java 1 1 100.00%
🔵 io/questdb/cutlass/line/tcp/LineTcpWriterJob.java 10 10 100.00%

@bluestreak01 bluestreak01 merged commit b82cc82 into master Jan 13, 2022
@bluestreak01 bluestreak01 deleted the ilp-fix-commit-timeout branch January 13, 2022 23:02
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.

None yet

3 participants