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

Multinode HA: status of stale chunks on a datanode #4848

Closed
nikkhils opened this issue Oct 18, 2022 · 0 comments · Fixed by #4971
Closed

Multinode HA: status of stale chunks on a datanode #4848

nikkhils opened this issue Oct 18, 2022 · 0 comments · Fixed by #4971
Assignees
@pmwkaa
Labels
feature-request Feature proposal
Milestone
TimescaleDB 2.9

Comments

@nikkhils
Copy link
Contributor

What problem does the new feature solve?

#4846 will remove metadata an Access node for a datanode (DN) that is down visavis a chunk on it that gets written to.

When such a DN comes back, it will have a list of chunks on it which have stale data, the DN needs to report back this list to the AN or additionally might also need to carry out any cleanup/maintenance locally.

What does the feature do?

The DN could report back the dimensions of chunks and then based on the discrepancies in the dimensions we can determine which chunk is stale on it.

Implementation challenges

No response
@nikkhils nikkhils added the feature-request Feature proposal label Oct 18, 2022
@nikkhils nikkhils mentioned this issue Oct 18, 2022
Closed
pmwkaa added a commit to pmwkaa/timescaledb that referenced this issue Nov 14, 2022
@pmwkaa
Introduce drop_stale_chunks() function
599a453 
This function drops chunks on a specified data node if those chunks are
not known by the access node.

Fix timescale#4848
@pmwkaa pmwkaa mentioned this issue Nov 14, 2022
Merged
@vineethapai vineethapai added this to the TimescaleDB 2.9 milestone Nov 15, 2022
pmwkaa added a commit to pmwkaa/timescaledb that referenced this issue Nov 17, 2022
@pmwkaa
Introduce drop_stale_chunks() function
19f6de9 
This function drops chunks on a specified data node if those chunks are
not known by the access node.

Fix timescale#4848
pmwkaa added a commit to pmwkaa/timescaledb that referenced this issue Nov 17, 2022
@pmwkaa
Introduce drop_stale_chunks() function
9345fb7 
This function drops chunks on a specified data node if those chunks are
not known by the access node.

Fix timescale#4848
pmwkaa added a commit to pmwkaa/timescaledb that referenced this issue Nov 17, 2022
@pmwkaa
Introduce drop_stale_chunks() function
dfcd336 
This function drops chunks on a specified data node if those chunks are
not known by the access node.

Fix timescale#4848
pmwkaa added a commit to pmwkaa/timescaledb that referenced this issue Nov 17, 2022
@pmwkaa
Introduce drop_stale_chunks() function
d98b415 
This function drops chunks on a specified data node if those chunks are
not known by the access node.

Fix timescale#4848
pmwkaa added a commit to pmwkaa/timescaledb that referenced this issue Nov 17, 2022
@pmwkaa
Introduce drop_stale_chunks() function
2f12293 
This function drops chunks on a specified data node if those chunks are
not known by the access node.

Fix timescale#4848
pmwkaa added a commit to pmwkaa/timescaledb that referenced this issue Nov 17, 2022
@pmwkaa
Introduce drop_stale_chunks() function
d5abea9 
This function drops chunks on a specified data node if those chunks are
not known by the access node.

Fix timescale#4848
pmwkaa added a commit to pmwkaa/timescaledb that referenced this issue Nov 17, 2022
@pmwkaa
Introduce drop_stale_chunks() function
d5e7c7c 
This function drops chunks on a specified data node if those chunks are
not known by the access node.

Fix timescale#4848
pmwkaa added a commit to pmwkaa/timescaledb that referenced this issue Nov 17, 2022
@pmwkaa
Introduce drop_stale_chunks() function
4a18a90 
This function drops chunks on a specified data node if those chunks are
not known by the access node.

Fix timescale#4848
pmwkaa added a commit to pmwkaa/timescaledb that referenced this issue Nov 21, 2022
@pmwkaa
Introduce drop_stale_chunks() function
e9dc8b3 
This function drops chunks on a specified data node if those chunks are
not known by the access node.

Fix timescale#4848
pmwkaa added a commit to pmwkaa/timescaledb that referenced this issue Nov 21, 2022
@pmwkaa
Introduce drop_stale_chunks() function
199c7f1 
This function drops chunks on a specified data node if those chunks are
not known by the access node.

Fix timescale#4848
pmwkaa added a commit to pmwkaa/timescaledb that referenced this issue Nov 22, 2022
@pmwkaa
Introduce drop_stale_chunks() function
43bfde5 
This function drops chunks on a specified data node if those chunks are
not known by the access node.

Call drop_stale_chunks() automatically when data node becomes
available again.

Fix timescale#4848
pmwkaa added a commit to pmwkaa/timescaledb that referenced this issue Nov 22, 2022
@pmwkaa
Introduce drop_stale_chunks() function
3a19491 
This function drops chunks on a specified data node if those chunks are
not known by the access node.

Call drop_stale_chunks() automatically when data node becomes
available again.

Fix timescale#4848
pmwkaa added a commit to pmwkaa/timescaledb that referenced this issue Nov 23, 2022
@pmwkaa
Introduce drop_stale_chunks() function
13e3e93 
This function drops chunks on a specified data node if those chunks are
not known by the access node.

Call drop_stale_chunks() automatically when data node becomes
available again.

Fix timescale#4848
pmwkaa added a commit to pmwkaa/timescaledb that referenced this issue Nov 23, 2022
@pmwkaa
Introduce drop_stale_chunks() function
7cbc436 
This function drops chunks on a specified data node if those chunks are
not known by the access node.

Call drop_stale_chunks() automatically when data node becomes
available again.

Fix timescale#4848
pmwkaa added a commit that referenced this issue Nov 23, 2022
@pmwkaa
Introduce drop_stale_chunks() function
5813173 
This function drops chunks on a specified data node if those chunks are
not known by the access node.

Call drop_stale_chunks() automatically when data node becomes
available again.

Fix #4848
SachinSetiya pushed a commit that referenced this issue Nov 28, 2022
@pmwkaa @SachinSetiya
Introduce drop_stale_chunks() function
5b29050 
This function drops chunks on a specified data node if those chunks are
not known by the access node.

Call drop_stale_chunks() automatically when data node becomes
available again.

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

@pmwkaa pmwkaa

Labels
feature-request Feature proposal
Projects
None yet
Milestone
TimescaleDB 2.9
Development

Successfully merging a pull request may close this issue.

Introduce drop_stale_chunks() function pmwkaa/timescaledb
3 participants
@pmwkaa @nikkhils @vineethapai