You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cassandra.apache.org by Shaurya Gupta <sh...@gmail.com> on 2021/06/04 08:47:47 UTC
Materialized Views during node replace
Hi
We recently replaced a down node containing 90 GB of data. The streaming
process completed within 1 hour as we could see a sufficient amount of data
being streamed on the data disk but the node remained in UJ state and it
took 7 more hours to move to UN state.
We could not figure out anything from system logs. Our DB schema contains 3
materialized views over the main table, could that be the reason for this?
If yes how can we be sure of it and if not then how do we figure out what
went wrong ?
Thanks!
--
Shaurya Gupta
Re: Materialized Views during node replace
Posted by Shaurya Gupta <sh...@gmail.com>.
Thanks!
Why are MVs being treated differently here ?
While node replace was ongoing sstables for MV also got streamed. Is
rebuilding the MV required to ensure consistency between main table and MVs
on the replaced node ?
On Fri, Jun 4, 2021 at 2:25 PM Erick Ramirez <er...@datastax.com>
wrote:
> I can't recall if view builds affect the bootstrap but index builds
> definitely do. It's a bit late now but you could've run nodetool
> compactionstats to see what tasks were running at the time and those need
> to complete before the bootstrap is considered complete for the node to go
> into UP/NORMAL status. Cheers!
>
--
Shaurya Gupta
Re: Materialized Views during node replace
Posted by Erick Ramirez <er...@datastax.com>.
I can't recall if view builds affect the bootstrap but index builds
definitely do. It's a bit late now but you could've run nodetool
compactionstats to see what tasks were running at the time and those need
to complete before the bootstrap is considered complete for the node to go
into UP/NORMAL status. Cheers!