Hi Justine,
Welcome to the community! There is quite an extensive playlist here from an
older DataStax Academy course on Cassandra admin:
https://www.youtube.com/playlist?list=PL2g2h-wyI4SrHMlHBJVe_or_Ryek2THgQ
An exact daily task list type video I haven't seen. In my experience the
fundamental
Hi Elliott,
Watching it now, this video is super super helpful, thanks for sharing. I was
however thinking more about day to day maintenance issues, maybe that topic is
not quite as sexy for a youtube video Maybe I should make one once I have
become a bit more experience under my belt.
>
I would avoid secondary indexes unless absolutely necessary. It will be
much better to have an efficient partition key + clustering key, as for any
given partition C* will know exactly what nodes to contact, whereas this
may not be the case with secondary indexes and you'll still likely need to
I'm a big fan of this one about LWTs:
https://www.youtube.com/watch?v=wcxQM3ZN20c
Not only if you want to understand LWTs, but also to get a better
understanding of the sometimes-unintuitive consistency promises made and
not made for non-LWT queries.
On Tue, Mar 16, 2021 at 11:53 PM wrote:
> I
Clear… Thanks for the detailed answer…
De : Jeff Jirsa
So, 30s or -Dcassandra.ring_delay_ms= on the command line, but note that this
ALSO impacts normal startup/shutdown/expand/shrink/etc type operations, and if
you have to ask how to change it, you probably shouldn't.
- Jeff
On 3.11, fat client timeout is QUARANTINE_DELAY / 2 :
https://github.com/apache/cassandra/blob/cassandra-3.11/src/java/org/apache/cassandra/gms/Gossiper.java#L260
Quarantine delay is StorageService.RING_DELAY * 2;
Thank you for this.
What about using a UUID for every row as the partition key and then a
secondary index for your time buckets instead of being part of the
partition key?
Example - say your buckets are 2021-03-15, 2021-03-16 etc... Your table:
create table whatever (uuid text, time_bucket
Hi Jeff
Thank a lot for your answer.
The reference to "fat client" is very interesting… On debug log on classical
node, we have sometimes message like :
INFO [GossipTasks:1] 2021-03-17 16:21:01,135 Gossiper.java:894 - FatClient
/10.120.1.183 has been silent for 3ms, removing from gossip
-Dcassandra.join_ring=false is basically a pre-bootstrap phase that says
"this machine is about to join the cluster, but hasn't yet, so don't give
it a token"
It's taking advantage of a stable but non-terminal state to let you do
things like serve queries without owning data - it's a side effect
Hi all,
Following a discussion with our adminsys, I have a very practical question.
We use cassandra proxies (-Dcassandra.join_ring=false) as coordinators for PHP
clients (a loot of PHP clients).
Our problem is that restarting Cassandra on proxies sometimes fails with the
following error :
Thanks - appreciate the tips!
> On 15 Mar 2021, at 22:42, Kane Wilson wrote:
>
> Keep in mind that you'll need the same tokens for each node for your restore
> to work if RF < #Nodes. There is an easy way to work around this though by
> setting RF=# of nodes on the system_auth keyspace (and
I know there is a lot of useful information out there, including on you tube. I
am looking for recommendations for good introductory (but detailed) videos
created by people who have cassandra cluster management, that outline all the
day to day activities someone who is managing a cluster would
12 matches
Mail list logo