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

Question on busy resource #398

Open
adrieng1977 opened this issue Jan 31, 2019 · 0 comments
Open

Question on busy resource #398

adrieng1977 opened this issue Jan 31, 2019 · 0 comments

Comments

@adrieng1977
Copy link

Hi
This is not really an issue but more so a question.

I am finally able to submit requests to my https services using ribbon.

First here are some of my constraints:
My remote services are single threaded and can only process 1 request at a time.
My remote services cannot scale at will.

What kind of setup should i use to have the incoming request wait for a service to be done with its task.
Is there a way to tell ribbon that when a service is used, that it is not available for others and that they should wait for 1 to be available.

I am currently using the IPing PingUrl to be more efficient in determining if a server is up or not, and I am using the IRule retryRule.

My service throws an exception when a new request is coming and that one is already being processed.

Would it make sense to have a custom IPing for that scenario?

thank you

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

1 participant