Hi ,
We are testing C* 3.11.3 and we have mapping issue and possibly leaked
memory.
It might be related to our configuration,any ideas would be helpful .
Cassandra version: 3.11.3
OS: CentOS Linux release 7.4.1708 (Core)
Kernel: 3.10.0-957.1.3.el7.x86_64
JDK: jdk1.8.0_131
Heap: same errors with
If you exceel 50% then you could be in trouble for compaction. No immediate
harm though, just that compaction will start failing and eventually, you
will see read latencies go high.
On Mon, Jan 14, 2019 at 4:59 AM Jinhua Luo wrote:
> But what if the sstable file size of the largest tire is too l
hi everyone,
I have activated DEBUG mode via nodetool setlogginglevel, now system.log
shows me slow queries (slower than 500ms) but the log is showing me the
wrong query. My query is composed like this:
SELECT pkey, f1, f2, f3 FROM mykeyspace.mytable WHERE pkey='xxx' LIMIT 3000;
but MonitoringTa
But what if the sstable file size of the largest tire is too large to
compact (e.g. no spare disk room to merge two huge sstables).
Not to mention that huge file is likely to bring troubles for some
file systems, and it's hard to backup them.
Nitan Kainth 于2019年1月14日周一 上午1:53写道：
>
> No, sstables
