Skip to content
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

enable retry in balancer_by_lua_block: need to set proxy_next_upstream_tries #90

Closed
fongx opened this issue Mar 7, 2017 · 5 comments
Closed

Comments

@fongx
Copy link

fongx commented Mar 7, 2017

hello, I find, in order to enable the retry, it needs to explicitly set the proxy_next_upstream_tries directive to a value greater than the default value, zero. I think it's a bug or at least it's incompatible with the original upstream failover policy. Because the document says the default zero value indicates that nginx won't limit the retry times other than disable the retry. If it's by design, its better to make it clearly in the document.

@agentzh
Copy link
Member

agentzh commented Mar 7, 2017

@fongx Will you try the latest master branch of lua-nginx-module?

@fongx fongx closed this as completed Mar 8, 2017
@fongx fongx reopened this Mar 8, 2017
@fongx
Copy link
Author

fongx commented Mar 8, 2017

I have the issue in the latest release openresty-1.11.2.2.tar.gz of lua-nginx-module but not test the latest master branch. Do you have merged any changes for this to the master branch since v1.11.2.2?

PS: sorry for the close and reopen by a mistaken click

@agentzh
Copy link
Member

agentzh commented Mar 8, 2017

@fongx IIRC, there is a related fix in the master. Why don't you try it out and/or check out the commit log history?

@fongx
Copy link
Author

fongx commented Mar 8, 2017

I checkout the latest master and install it on a new machine. But it's weired, the problem seems unresolved. Yes, I find the patch have been applied at 853. Maybe I still miss something else. I will check more and then come back.

@fongx
Copy link
Author

fongx commented Mar 8, 2017

BINGO. It's fixed in the latest master branch. Thanks.

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

No branches or pull requests

2 participants