Yep, also use Ansible with configs living in git here.
On Fri, Oct 15, 2021 at 5:19 PM Bowen Song wrote:
> We have Cassandra on bare-metal servers, and we manage our servers via
> Ansible. In this use case, we create an Ansible playbook to update the
> servers one by one, change the
You ran the `alter keyspace` command on the original dc1 nodes or the new
dc2 nodes?
On Wed, Oct 13, 2021 at 8:15 AM Stefan Miklosovic <
stefan.mikloso...@instaclustr.com> wrote:
> Hi Tom,
>
> while I am not completely sure what might cause your issue, I just
> want to highlight that schema
Hmm. are the ports open on the `new` server?
Looks like it can connect to other nodes but other nodes can't connect to
it.
-Vy
On Fri, Sep 10, 2021 at 10:20 AM Joe Obernberger <
joseph.obernber...@gmail.com> wrote:
> Good idea.
> There are two seed nodes:
> I see this on one (note
The process line looks like it's missing all the cassandra jars, what
command is the `service cassandra start` running?
On Thu, Aug 19, 2021 at 8:18 AM FERON Matthieu wrote:
> Thanks for your help. I've looked the docker logs for the container but
> didn't ffound nothing helpfull
>
You might want to take a look at `unchecked_tombstone_compaction` table
setting. The best way to see if this is affecting you is to look at the
sstablemetadata for the sstables and see if your tombstone ratio is higher
than the configured tombstone_threshold ratio (0.2 be default) for the
table.
I believe you could set your tables to flush to disk at specific intervals
(memtable_flush_period_in_ms), note that you'd have to set this for all
tables (not just the CDC enabled tables) to ensure that commitlog files are
flushed to the cdc_raw directory. Or as Dhanunjaya noted you could just
17ms read latency for the 50th percentile is actually a pretty high latency
in my experience, I prefer to see the 75th percentile read latency to be
around 1-2ms. Of course it depends on your use case and what your
performance objectives are.
On Thu, Apr 29, 2021 at 7:05 AM Kane Wilson wrote:
