You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
BugFix: 1.0 Ingesters having availability zone value erased by pre-1.0 ingesters during rolling upgrade. (#2404)
* When executing updateConsul for an existing ingester, ensure to write the zone on the updated record
Signed-off-by: Ken Haines <khaines@microsoft.com>
* adding unit test checking that the zone value is updated when an external actor clears it
Signed-off-by: Ken Haines <khaines@microsoft.com>
* updating CHANGELOG.md
Signed-off-by: Ken Haines <khaines@microsoft.com>
* removing internal default 'no-zone' value of lifecyler.id and leaving a blank string
Signed-off-by: Ken Haines <khaines@microsoft.com>
*[BUGFIX] Experimental TSDB: fixed response status code from `422` to `500` when an error occurs while iterating chunks with the experimental blocks storage. #2402
20
+
*[BUGFIX] Ring: Fixed a situation where upgrading from pre-1.0 cortex with a rolling strategy caused new 1.0 ingesters to lose their zone value in the ring until manually forced to re-register. #2404
0 commit comments