TLS and lockstate, fault tolerance metrics#48
Merged
pboros merged 4 commits intotigrisdata:mainfrom Mar 31, 2025
Merged
Conversation
czephyr
changed the title
Collaborator
|
This is great, thank you for your contributions. I also tested this on our development systems and it works as expected, I did not test the TLS part. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I added some metrics about the state health of the cluster, as well as lockstate and fault tolerance metrics.
I also added some logic in the database connection to be able to work in a TLS environment.
Refactored the Dockefile to work with multiclient libraries and to be able to use layer caching.
The resulting build is currently being used on my clusters.