Look into how upgrade handles running processes
- Dominant language
- Java
- Stars
- 1.2k
- Forks
- 487
- Avg merge
- 4d 5h
- Merged PRs (30d)
- 13
Description
I think the expectation when someone does an Accumulo upgrade is that all Accumulo processes are killed across the cluster before starting the new version of Accumulo. However, what if anything is done to handle a situation like the following.
* Some 1.9.3 tablet servers are running and have metadata tablets assigned to them
* A 2.0.0 master process is started and it starts working on upgrade.
What will happen in this situation? I think ideally the 2.0.0 master process would log an error message about the 1.9.3 tservers, take no upgrade actions, and terminate itself.
Contributor guide
Research direction
Trace the upgrade startup path and process-version checks for the mixed 1.9.3 tablet server and 2.0.0 master scenario described here. Determine the current behavior, then verify that an incompatible running process is reported, upgrade actions are skipped, and the master terminates safely.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100