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.

Sign up for GitHub

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

Jump to bottom

Maintenance procedure in multidatabase multinode setup #3433

Closed
thedolphin opened this issue Jul 22, 2021 · 1 comment · Fixed by #3440
Closed

Maintenance procedure in multidatabase multinode setup #3433

thedolphin opened this issue Jul 22, 2021 · 1 comment · Fixed by #3440
Assignees
@pmwkaa
Labels
bug multinode

Comments

@thedolphin
Copy link

Relevant system information:

  • OS: docker image pg13.3-ts2.3.0-latest
  • PostgreSQL version (output of postgres --version): 13.3
  • TimescaleDB version (output of \dx in psql): 2.3.0
  • Installation method: using Docker

Describe the bug
More then one database in multinode setup causes maintenance procedure to stop working with message "ERROR: [datanode1]: prepared transaction belongs to another database".

Seems the query has to be more specific and include database name

To Reproduce
Steps to reproduce the behavior:
Install TSDB in multinode
Create two or mode databases with distributed hypertabes, execute maintenance task

Expected behavior
Maintenance procedure works without errors

Actual behavior
Maintenance procedure stops with error "ERROR: [datanode1]: prepared transaction belongs to another database".
@pmwkaa
Copy link
Contributor

pmwkaa commented Jul 23, 2021

Thanks for posting! seems like a bug

@pmwkaa pmwkaa self-assigned this Jul 23, 2021
pmwkaa added a commit to pmwkaa/timescaledb that referenced this issue Jul 25, 2021
@pmwkaa
Fix remote_txn_heal_data_node() for multiple DB's
21246d4 
Since pg_prepared_xacts is shared between databases, the healing
function tried to resolve prepared transactions created by other
distributed databases.

This change makes the healing function to work only with current
database.

Fix timescale#3433
@pmwkaa pmwkaa mentioned this issue Jul 25, 2021
Merged
pmwkaa added a commit that referenced this issue Jul 26, 2021
@pmwkaa
Fix remote_txn_heal_data_node() for multiple DB's
bad2fc1 
Since pg_prepared_xacts is shared between databases, the healing
function tried to resolve prepared transactions created by other
distributed databases.

This change makes the healing function to work only with current
database.

Fix #3433
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@pmwkaa pmwkaa

Labels
bug multinode
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix remote_txn_heal_data_node() for multiple DB's pmwkaa/timescaledb
2 participants
@pmwkaa @thedolphin