Do I need clock synchronisation for cassandra if only one client writes to cluster? -


from cassandra's documentation got know cassandra uses timestamps of query resolve conflicts between 2 writes , hence clocks on nodes of cluster needs synchronised. in use-case have 1 client writing cluster , multiple clients reading cluster. so, if use client-side timestamp generator (which believe default version>3) still need have cluster node clocks synchronised each other?

in context of write timestamps associated data being stored, clock synchronization not needed if using client timestamps , single client.

however, still discourage not @ least trying keep clocks in sync in cassandra cluster. there have been cases clock skew affects other parts of cassandra. example, cassandra-11991 shows case clock skew effected node clocks used light weight transactions. while particular issue has been addressed, still seems idea make effort synchronize.


Comments

Popular posts from this blog

php - Permission denied. Laravel linux server -

google bigquery - Delta between query execution time and Java query call to finish -

python - Pandas two dataframes multiplication? -