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
[Feature]: Add timeout support to the ping_data_node function #5312
Labels
enhancement
An enhancement to an existing feature for functionality
Comments
pmwkaa
added
the
enhancement
An enhancement to an existing feature for functionality
label
Feb 13, 2023
pmwkaa
added a commit
to pmwkaa/timescaledb
that referenced
this issue
Feb 13, 2023
This PR introduces a timeout argument and a new logic to the timescale_internal.ping_data_node() function which allows to handle io timeouts for nodes being unresponsive. Fix timescale#5312
pmwkaa
changed the title
Add timeout support to the ping_data_node function
[Feature]: Add timeout support to the ping_data_node function
Feb 15, 2023
pmwkaa
added a commit
to pmwkaa/timescaledb
that referenced
this issue
Feb 15, 2023
This PR introduces a timeout argument and a new logic to the timescale_internal.ping_data_node() function which allows to handle io timeouts for nodes being unresponsive. Fix timescale#5312
pmwkaa
added a commit
to pmwkaa/timescaledb
that referenced
this issue
Feb 15, 2023
This PR introduces a timeout argument and a new logic to the timescale_internal.ping_data_node() function which allows to handle io timeouts for nodes being unresponsive. Fix timescale#5312
pmwkaa
added a commit
to pmwkaa/timescaledb
that referenced
this issue
Feb 15, 2023
This PR introduces a timeout argument and a new logic to the timescale_internal.ping_data_node() function which allows to handle io timeouts for nodes being unresponsive. Fix timescale#5312
pmwkaa
added a commit
to pmwkaa/timescaledb
that referenced
this issue
Feb 15, 2023
This PR introduces a timeout argument and a new logic to the timescale_internal.ping_data_node() function which allows to handle io timeouts for nodes being unresponsive. Fix timescale#5312
pmwkaa
added a commit
to pmwkaa/timescaledb
that referenced
this issue
Feb 15, 2023
This PR introduces a timeout argument and a new logic to the timescale_internal.ping_data_node() function which allows to handle io timeouts for nodes being unresponsive. Fix timescale#5312
pmwkaa
added a commit
to pmwkaa/timescaledb
that referenced
this issue
Feb 15, 2023
This PR introduces a timeout argument and a new logic to the timescale_internal.ping_data_node() function which allows to handle io timeouts for nodes being unresponsive. Fix timescale#5312
pmwkaa
added a commit
to pmwkaa/timescaledb
that referenced
this issue
Feb 15, 2023
This PR introduces a timeout argument and a new logic to the timescale_internal.ping_data_node() function which allows to handle io timeouts for nodes being unresponsive. Fix timescale#5312
pmwkaa
added a commit
to pmwkaa/timescaledb
that referenced
this issue
Feb 21, 2023
This PR introduces a timeout argument and a new logic to the timescale_internal.ping_data_node() function which allows to handle io timeouts for nodes being unresponsive. Fix timescale#5312
pmwkaa
added a commit
to pmwkaa/timescaledb
that referenced
this issue
Feb 21, 2023
This PR introduces a timeout argument and a new logic to the timescale_internal.ping_data_node() function which allows to handle io timeouts for nodes being unresponsive. Fix timescale#5312
pmwkaa
added a commit
that referenced
this issue
Feb 21, 2023
This PR introduces a timeout argument and a new logic to the timescale_internal.ping_data_node() function which allows to handle io timeouts for nodes being unresponsive. Fix #5312
akuzm
pushed a commit
to akuzm/timescaledb
that referenced
this issue
Mar 27, 2023
This PR introduces a timeout argument and a new logic to the timescale_internal.ping_data_node() function which allows to handle io timeouts for nodes being unresponsive. Fix timescale#5312
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What type of enhancement is this?
API improvement, Tech debt reduction, User experience
What subsystems and features will be improved?
Data node
What does the enhancement do?
Add a way to specify ping out for the ping_data_node function by reaching which function should return false instead of being blocked
Implementation challenges
No response
The text was updated successfully, but these errors were encountered: