Test #380
Closed
Test #380
Conversation
This file contains 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
…-query HA: Add own instance ID to responsibility query
Sync overdue indicators
Survive a Redis restart
These updates must be executed in order, therefore prevent concurrency by using a separate semaphore.
…currency Don't execute runtime update upset queries concurrently
Wrap Redis errors
…-sql-schema Change ID fields to match SQL schema
Re-use Redis dialer logic in retry.WithBackoff() and the SQL driver
Query() returns a cursor that has to be closed to not block the underlying database connection. Use ExecContext() instead to both avoid the cursor leak and also properly pass the context. This bug lead to the DB connection pool be blocked completely after a certain number of runtime delete queries.
db.BulkExec(): Use ExecContext() instead of Query()
Only log after the third retry with the info level. Also, before executing the transaction, sleep dependent on the retry count.
Improve database and HA logging
Include Github Actions
This fixes a data race where the pairs channel was closed too early when the context is canceled and therefore the outer errgroup returns from Redis operations before Wait() is called on the inner errgroup. Unfinished Go methods in the inner errgroup would then try to work on a closed channel.
Use a buffered channel so that the next HSCAN call does not have to wait until the previous result has been processed.
Fix use of wrong log function on heartbeat loss
Use uint64 as there is no longer any concurrent access.
Fix data races
... to give the admin the all-clear. refs #351
…/zap-1.19.1 Bump go.uber.org/zap from 1.19.0 to 1.19.1
Redis HYield: remove duplicates returned by HSCAN
Log all different failed and recovered reconnects to backends
Rewrite delta to use only a single goroutine
…e-160 Include CheckResult#scheduling_source in state and history
... to make MySQL storage capabilities of likely large text columns more similar (16MB -> 4GB) to (upcoming) Postgres ones (unlimited) and not to have to pre-truncate anything. refs #260
We already have config.yml.example as a source to copy and paste so one can get started easily. In addition, only one place has to be maintained for the example configuration.
Remove example configuration from docs
This now also uses info as the default log level and enables the configuration of the default log level as well as log levels of the child loggers that will be implemented in a later commit.
Schema: s/mediumtext/longtext/
Child loggers
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.