Skip to content

Retry when pool is full#26

Merged
zuiderkwast merged 2 commits intoNordix:nordix-devfrom
zuiderkwast:pool_full
Sep 18, 2020
Merged

Retry when pool is full#26
zuiderkwast merged 2 commits intoNordix:nordix-devfrom
zuiderkwast:pool_full

Conversation

@zuiderkwast
Copy link
Collaborator

Fixes adrienmo#28 and obsoletes PR adrienmo#29.

Retry is implemented for query, but not for query_noreply. Perhaps it should.

Fixes adrienmo#28 and obsoletes PR adrienmo#29.

Retry is implemented for query, but not for query_noreply. Perhaps it should.
@bjosv
Copy link
Collaborator

bjosv commented Sep 17, 2020

Might be possible to test the flow aswell if a testcase sets

application:set_env(eredis_cluster, pool_size, 0),
application:set_env(eredis_cluster, pool_max_overflow, 0),

..but queries (which I think should cover the full case) might result in the same error as other faults, ie, {error, no_connection}
Would be nice to have it covered for future changes

@zuiderkwast
Copy link
Collaborator Author

Can we have a fakeredis which sleeps for some seconds when performing the query? Then we can have a pool size of 1 and two concurrent queries.

@bjosv
Copy link
Collaborator

bjosv commented Sep 18, 2020

sounds good, without the correction the second query should not be retried and fail I guess

@bjosv
Copy link
Collaborator

bjosv commented Sep 18, 2020

Nice! Lgtm

@zuiderkwast zuiderkwast merged commit 90d7f4c into Nordix:nordix-dev Sep 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Error in call to query when pool is full

2 participants