Skip to content

Conversation

@gazi-yestemirova
Copy link
Contributor

What changed?

  • Updated executor so Stop() sends the final heartbeat with "DRAINING" status. This keeps shard ownership metadata consistent when an executor shuts down.
  • Updated canary app's fx to use Decorate instead of Invoke in order to start and stop the dispatcher at the correct time.

Why?
Shard-distributor should be notified about the executors that are shutting down to reassign the shards and keep track of ownership.

How did you test it?
unit-tests and local testing with etcd

Potential risks

Release notes

Documentation Changes

Signed-off-by: Gaziza Yestemirova <gaziza@uber.com>
Signed-off-by: Gaziza Yestemirova <gaziza@uber.com>
Signed-off-by: Gaziza Yestemirova <gaziza@uber.com>
executorID: "test-executor-id",
timeSource: timeSource,
}
}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice!

t.Fatal("stopC should not be closed")
default:
}
}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we want it to be the same. In hindsight we should have just used context cancellation to stop.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

makes sense! let me update the test

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