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

The instances aren't synchronising after configuration change #13

Open
Vishal-Joshi opened this issue Mar 3, 2016 · 1 comment
Open

Comments

@Vishal-Joshi
Copy link

Hi,

I have some instances in a cluster and I see that they don't get synchronised after I update some hystrix configurations even after the 'delay' time duration. The reason I found is we have to select 'Execution Isolation Strategy' so that the instances start taking the new configurations. There is no pointer to the user about why instances are being shown Unsynchronised.

The 'Execution Isolation Strategy' should come selected by default.

Regards,
Vishal Joshi

@Vishal-Joshi Vishal-Joshi changed the title The instances doesn't get synchronised after configuration change The instances aren't synchronising after configuration change Mar 3, 2016
@chrisgray chrisgray added this to the 0.3.4 milestone Mar 9, 2016
@chrisgray
Copy link
Contributor

You're definitely right in that they aren't appearing to be synchronized until you select a "Execution Isolation Strategy".

To be clear, the instances are synchronizing each of the individual settings just Breakerbox isn't giving you that full 100% synchronized because the execution isolation strategy isn't set Breakerbox side.

This was done intentionally because we added the ability to configure Execution Isolation Strategy later. So you might have multiple configurations in the past without it being set explicitly by a user. In order to set it for you Breakerbox would have to "auto-fill" this field if it's absent Breakerbox side from configurations it's retrieving from the remote instance(s).

I'll go ahead and make this an issue to be fixed in a future release. I agree that this will help with clarity and confusion around whether or not a configuration is synchronized or not.

@chrisgray chrisgray modified the milestones: 0.3.5, 0.3.4 Mar 23, 2016
@chrisgray chrisgray modified the milestones: 0.3.5, 0.4.3 Apr 19, 2016
chrisgray pushed a commit that referenced this issue Aug 22, 2016
@chrisgray chrisgray removed this from the 0.4.4 milestone Oct 10, 2016
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