Re: Enable audit log

gt;> >> >> https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/audit/AuditLogManager.java#L204 >> >> On Tue, Jan 14, 2025 at 4:21 PM Sebastian Albrecht < >> sebastian.albre...@agido.com> wrote: >> >>> Hi, >>>

Re: Enable audit log

Miklošovič > wrote: > >> Hi Sebastian, >> >> the behaviour you see seems to be a conscious decision: >> >> >> https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/audit/AuditLogManager.java#L204 >> >> On Tue, Jan 14

Enable audit log

Hi, i am using cassandra 4.1 and i want activate audit logging. I set the following values in cassandra.yml and expect that logging starts after the next cassandra start: audit_logging_options: enabled: true logger: - class_name: FileAuditLogger included_categories: DCL, ERROR, AUTH Afte

Re: Upgrade 3.11.6 to 4.0.3, commitlog warns

Am Fr., 13. Mai 2022 um 12:05 Uhr schrieb Erick Ramirez < erickramire...@apache.org>: > It's expected and is nothing to worry about. From C* 3.0.25/3.11.11/4.0, > the SSTables now contain the host ID on which they were created to prevent > loss of commitlog data when SSTables are moved/copied to o

Upgrade 3.11.6 to 4.0.3, commitlog warns

Hi, i just upgraded my one-node cassandra from 3.11.6 to 4.0.3. Now every time it starts it's producing the following warn messages in the log like: WARN [main] 2022-01-18 10:55:00,696 CommitLogReplayer.java:305 - Origin of 2 sstables is unknown or doesn't match the local node; commitLogIntervals f