Skip to content

Enough reconnection retry before flushing out offline queue#362

Closed
vedratna-velani wants to merge 1 commit into
redis:masterfrom
vedratna-velani:master
Closed

Enough reconnection retry before flushing out offline queue#362
vedratna-velani wants to merge 1 commit into
redis:masterfrom
vedratna-velani:master

Conversation

@vedratna-velani

Copy link
Copy Markdown

I came across the scenario where under heavy traffic or due to some connection issue, got redis connection error and redis command just fails with error. Instead I think it should have an option to retry enough before error out the command.

@brycebaril

Copy link
Copy Markdown
Contributor

I've also hit this myself -- #280 so I agree this is important. We may want to consider a couple things though:

1: Is there a reasonable default value we could set for this new option?
2: Any chance you could add some tests that show it behaves correctly before/after the option threshold?

Comment thread index.js

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

checking that it is greater than zero should be enough? Or just set it to -1 as the default value.

BridgeAR added a commit that referenced this pull request Sep 16, 2015
Implement redis connection broken mode and more shiny things

Fixes #569
Fixes #587
Fixes #566 
Fixes #586 
Fixes #280 

This includes the fixes as suggested in #671, #615 and #533. Thx a lot to @qdb, @tobek and @chrishamant 

Closes #675, #463, #362, #438 and #724
@BridgeAR

Copy link
Copy Markdown
Contributor

Thx a lot for your work but closing this in favor of #829.

@BridgeAR BridgeAR closed this Sep 16, 2015
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.

4 participants