It’s a warning, but probably not causing you problems
A 20kB batch is a hint that your batches are larger than Cassandra expects, but
the 5k limit for that logger was somewhat arbitrary, and I would be shocked if
20kB batches were a problem unless you were already close to tipping your
cluster
cassandro nodes restarts
we see errors typically like these
WARN [Native-Transport-Requests-3] 2018-07-25 20:51:38,520
BatchStatement.java:301 - Batch for "keyspace.table"
is of size 19.386KiB, exceeding specified threshold of 5.000KiB by
14.386KiB.
Regards
R1J1
Feel free to file issues at
https://github.com/thelastpickle/cassandra-reaper/issues
or chat with us at https://gitter.im/thelastpickle/cassandra-reaper
regards,
Mick
On Thu, 26 Jul 2018, at 06:18, Abdul Patel wrote:
> Was abke start it but unable to start any repair manually it says
>
Was abke start it but unable to start any repair manually it says
POST/repair_run
Unit conflits with exiting in clustername
On Wednesday, July 25, 2018, Abdul Patel wrote:
> Ignore , alter and create permission were missing ..will msg if i actually
> see an showstopper
>
> On Wednesday, July
Ignore , alter and create permission were missing ..will msg if i actually
see an showstopper
On Wednesday, July 25, 2018, Abdul Patel wrote:
> I am trying to uograde to 1.2.2 version of reaper the instance isnt
> starting and giving error that unable to create table snapshot ..do we need
> to
I am trying to uograde to 1.2.2 version of reaper the instance isnt
starting and giving error that unable to create table snapshot ..do we need
to create it under reaper-db?
On Wednesday, July 25, 2018, Steinmaurer, Thomas <
thomas.steinmau...@dynatrace.com> wrote:
> Jon,
>
>
>
> eager trying it
nodetool compactionstats --- see compacting which table
nodetool cfstats keyspace_name.table_name --- check partition side,
tombstones
go the data file directories: look the data file size, timestamp, ---
compaction will write to new temp file with _tmplink...,
use sstablemetadata ...
I'm using 3.0.15. I see that there is some fix for sstable metadata in
3.0.16 https://issues.apache.org/jira/browse/CASSANDRA-14217 - is that a
fix for "reading cardinalyti from statistics.db" ?
On Wed, Jul 25, 2018 at 1:02 PM Hannu Kröger wrote:
> What version of Cassandra are you running?
Hi,
we have a table which is being compacted all the time, with no change in size:
Compaction History:
compacted_atbytes_inbytes_out rows_merged
2018-07-25T05:26:48.101 57248063878 57248063878 {1:11655}
2018-07-25T01:09:47.346 57248063878 57248063878
{1:11655}
What version of Cassandra are you running? There is a bug in 3.10.0 and certain
3.0.x that occurs in certain conditions and corrupts that file.
Hannu
> Vitali Dyachuk kirjoitti 25.7.2018 kello 10.48:
>
> Hi,
> I have noticed in the cassandra system.log that there is some issue with
>
Jon,
eager trying it out. Just FYI. Followed the installation instructions on
http://cassandra-reaper.io/docs/download/install/ Debian-based.
1) Importing the key results in:
XXX:~$ sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys
2895100917357435
Executing:
Hi,
I have noticed in the cassandra system.log that there is some issue with
sstable metadata, the messages says:
WARN [Thread-6] 2018-07-25 07:12:47,928 SSTableReader.java:249 - Reading
cardinality from Statistics.db failed for
/opt/data/disk5/data/keyspace/table/mc-big-Data.db
Although there is
13 matches
Mail list logo
