THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
JIRA:
| Jira | ||||||
|---|---|---|---|---|---|---|
|
Discussion: here
Motivation
Currently, when expanding the KS cluster, the new node's partitions will be unavailable during the rebalance, which for large states can take a very long time, or for small state stores even more than a few ms can be a deal-breaker for microservice use cases. Basically, as soon as a task is assigned to the new node, it initializes the store and opens it. Post it the task is moved to Restoring state where it could take time to restore all the data from the changelog topic depending upon data in that partition and then it will transition to the Running state and is available to serve the queries. As of now, the tasks serve data only when they are in the Running state.
...