Maintenance of Hystrix

[andys...@gmail.com]

Hi

There are two issues introduced in 1.5.12:

1. A race condition that can prevent a circuit from reopening after closing https://github.com/Netflix/Hystrix/issues/1633

2. An issue that prevents ConcurrencyStrategy working on Hystrix timeouts https://github.com/Netflix/Hystrix/issues/1767

The race condition has been known about for over a year and there are a few duplicates of this issue. There even appears to be a PR to fix it: https://github.com/Netflix/Hystrix/pull/1640. I'm not aware of a fix for the second one, but the issue has been open since the beginning of this year.

The solution in both cases seems to be to downgrade to 1.5.11. The current version of Hystrix (released in May this year) is 1.5.13.

My questions then:

1. Is Hystrix actively maintained?

2. If so, are you aware of these issues and would you like some help fixing these issues?

3. If not (and just out of interest) what approach are Netflix taking with client side circuit breaking?

Thanks,

-Andy

[Andy Stanton]

edit: the current version of Hystrix was released in July 2017. It was the most recent commit that was May this year.

[Kristine Jetzke]

Glad I'm not the only one looking for those answers... 

I was able to contact the previous maintainer on twitter. He suggested to contact https://twitter.com/timbozarth but I had no luck so far. I added a comment to Future of Hystrix GitHub issue but no reply.

I also wrote an email to https://github.com/drobertduke because he was one of the last people from Netflix to make a commit. No reply.

I tried emailing and tweeting to HystrixOSS but also no reply and that was more than 1 month ago (https://twitter.com/tinejetzke/status/1044954184188133383).

Not really sure what else to do...