I’m using Quest Foglight, very good if you have budget for it??
Jonathan Baynes
DBA
Tradeweb Europe Limited
Moor Place • 1 Fore Street Avenue • London EC2Y 9DT
P +44 (0)20 77760988 • F +44 (0)20 7776 3201 • M +44 (0)7884111546
jonathan.bay...@tradeweb.com
I’ve collected a bunch at http://leaves.anant.us/#!/?tag=cassandra,monitoring
I reommend Grafana / Prometheus if you don’t have DSE (which has OpsCenter)
--
Rahul Singh
rahul.si...@anant.us
Anant Corporation
On Jun 19, 2018, 1:06 PM -0400, Romain Gérard , wrote:
> Hi Felipe,
>
> You can use
Queues can be implemented in Cassandra even though everyone believes its an
“anti-pattern” if the design is designed for Cassandra’s model.
In this case, I would do a logical / soft delete on the data to invalidate it
from a query that accesses it and put a TTL on the data so it deletes
A read before write is always going to be tremendously more than just writing.
Depending on your architecture you may consider both of the options described.
If you have a CQRS architecture and are processing an event queue — doing LWT /
read before write , then your “write” is processed
Hi,
Another way would be to make your PK a clustering key with Id as PK and time as
clustering with type TimeUUID. Then you’ll always insert records, never update,
for each “transaction” you’ll keep a row in the partition. Then when you’ll
read all the rows for that partition by Id, you’ll
In the previous message, I have pasted source code from cassandra 2.2.8 by
mistake.
Re-checked for 2.2.11 source.
These lines are the same.
2018-06-21 2:49 GMT+05:00 Dmitry Simonov :
> Hello!
>
> Using Cassandra 2.2.11, I observe behaviour, that is very similar to
>
