Skip to content

Fix for Semaphore vs Thread Isolation Bug#238

Merged
benjchristensen merged 2 commits intoNetflix:masterfrom
benjchristensen:semaphore-vs-thread-isolation
Apr 1, 2014
Merged

Fix for Semaphore vs Thread Isolation Bug#238
benjchristensen merged 2 commits intoNetflix:masterfrom
benjchristensen:semaphore-vs-thread-isolation

Conversation

@benjchristensen
Copy link
Copy Markdown
Contributor

Fix for #232 where SEMAPHORE and THREAD rejection rules were both being applied at the same time after the HystrixObservableCommand refactor.

- Use `Immediate` so that we don't add scheduling overhead unless needed.
- Reuse the Hystrix thread if it is there. The computation of the callback can be part of the Hystrix thread.
- No one using Hystrix+Observable should be doing anything blocking on those callbacks.
- only SEMAPHORE reject if SEMAPHORE isolation is being used
- unit test to assert that THREAD and SEMAPHORE isolation reject independently of each other
@cloudbees-pull-request-builder
Copy link
Copy Markdown

Hystrix-pull-requests #109 FAILURE
Looks like there's a problem with this pull request

@benjchristensen
Copy link
Copy Markdown
Contributor Author

The build failure was something to do with javadoc ... going to stop javadocs from being generated as they are not needed and irritating in how fragile they are.

benjchristensen added a commit that referenced this pull request Apr 1, 2014
…ation

Fix for Semaphore vs Thread Isolation Bug
@benjchristensen benjchristensen merged commit 041c2f9 into Netflix:master Apr 1, 2014
@benjchristensen benjchristensen deleted the semaphore-vs-thread-isolation branch April 1, 2014 03:48
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.

2 participants