Botond Dénes
Botond Dénes
> The required nr_event (1) exceeds the limit of request capacity in /proc/sys/fs/aio-max-nr (65536) This message makes sense. The current limit is `65536`, yet nodetool fails to obtain its `1`...
> > > The required nr_event (1) exceeds the limit of request capacity in /proc/sys/fs/aio-max-nr (65536) > > > > > > This message makes sense. The current limit is...
Ok, I think I found a bug in seastar related to this.
seastar bug which causes this failing check: https://github.com/scylladb/seastar/issues/2453.
> [@denesb](https://github.com/denesb) Any idea? No idea. Can you add `--logger-log-level seastar=trace` to the `nodetool` command line, so we can see what it is doing?
> [@denesb](https://github.com/denesb) > > `/home/scylla-test/scylladb/bin/nodetool --logger-log-level seastar=trace status` doesn't seem to work... I have no idea how to pass this into the tool. > > I would suggest someone would...
> [test_snapshot_cursor_is_consistent_with_merging](https://jenkins.scylladb.com//job/scylla-6.0/job/scylla-ci/191/testReport/junit/boost/mvcc_test/test_snapshot_cursor_is_consistent_with_merging) [🔍](https://github.com/scylladb/scylladb/issues?q=is:issue+is:open+test_snapshot_cursor_is_consistent_with_merging) https://github.com/scylladb/scylladb/issues/13642
> What about `crc_check_chance`? I'm not sure there's much value in supporting it, but it can be a way to disable the feature. Unfortunately `crc_check_chance` is a compression option. We...
> Let's add a configuration option instead; so that if this turns out to be a performance regression, it can be disabled in the field. There are two reasons for...