mirror of https://github.com/hashicorp/consul
9f7626d501
Ensure all topics are refreshed on FSM restore and add supervisor loop to v1 controller subscriptions This PR fixes two issues: 1. Not all streams were force closed whenever a snapshot restore happened. This means that anything consuming data from the stream (controllers, queries, etc) were unaware that the data they have is potentially stale / invalid. This first part ensures that all topics are purged. 2. The v1 controllers did not properly handle stream errors (which are likely to appear much more often due to 1 above) and so it introduces a supervisor thread to restart the watches when these errors occur. |
||
|---|---|---|
| .. | ||
| event.go | ||
| event_buffer.go | ||
| event_buffer_test.go | ||
| event_publisher.go | ||
| event_publisher_test.go | ||
| event_snapshot.go | ||
| event_snapshot_test.go | ||
| event_test.go | ||
| noop.go | ||
| string_types.go | ||
| subscription.go | ||
| subscription_test.go | ||