You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cassandra.apache.org by Carl Mueller <ca...@smartthings.com.INVALID> on 2018/10/30 15:35:03 UTC

comprehensive list of checks before rolling version upgrades

Does anyone have a pretty comprehensive list of these? Many that I don't
currently know how to check but I'm researching...

I've seen:

- verify disk space available for snapshot + sstablerewrite
- gossip state agreement, all nodes are healthy
- schema state agreement
- ability to access all the nodes
- no repairs, upgradesstables, and cleans underway
- read repair/hinted handoff is not backed up

Other possibles:
- repair state? can we get away with unrepaired data?
- pending tasks?
- streaming state/tasks?

Re: comprehensive list of checks before rolling version upgrades

Posted by DuyHai Doan <do...@gmail.com>.
To add to your excellent list:

- no topology change (joining/leaving/decommissioning) nodes
- no rebuild of index/MV under way

On Tue, Oct 30, 2018 at 4:35 PM Carl Mueller
<ca...@smartthings.com.invalid> wrote:

> Does anyone have a pretty comprehensive list of these? Many that I don't
> currently know how to check but I'm researching...
>
> I've seen:
>
> - verify disk space available for snapshot + sstablerewrite
> - gossip state agreement, all nodes are healthy
> - schema state agreement
> - ability to access all the nodes
> - no repairs, upgradesstables, and cleans underway
> - read repair/hinted handoff is not backed up
>
> Other possibles:
> - repair state? can we get away with unrepaired data?
> - pending tasks?
> - streaming state/tasks?
>
>