Re: [ceph-users] What do internal_safe_to_start_threads and leveldb_compression do?
On Tue, Jun 2, 2015 at 6:47 AM, Erik Logtenberg e...@logtenberg.eu wrote: What does this do? - leveldb_compression: false (default: true) - leveldb_block/cache/write_buffer_size (all bigger than default) I take it you're running these commands on a monitor (from I think the Dumpling timeframe, or maybe even Firefly)? These are hitting specific settings in LevelDB which we tune differently for the monitor and OSD, but which were shared config options in older releases. They have their own settings in newer code. -Greg You are correct. I started out with Firefly and gradually upgraded the cluster as new releases came out. I am on Hammer (0.94.1) now. The current settings are different from the default. Does this mean that the settings are still Firefly-like and should be changed to the new default; or does this mean that the defaults are still Firefly-like but the settings are actually Hammer-style ;) and thus right. Hmm, I think you must be setting them in your config file for them to be different now, but I don't really remember...Joao? :) -Greg ___ ceph-users mailing list ceph-users@lists.ceph.com http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
Re: [ceph-users] What do internal_safe_to_start_threads and leveldb_compression do?
What does this do? - leveldb_compression: false (default: true) - leveldb_block/cache/write_buffer_size (all bigger than default) I take it you're running these commands on a monitor (from I think the Dumpling timeframe, or maybe even Firefly)? These are hitting specific settings in LevelDB which we tune differently for the monitor and OSD, but which were shared config options in older releases. They have their own settings in newer code. -Greg You are correct. I started out with Firefly and gradually upgraded the cluster as new releases came out. I am on Hammer (0.94.1) now. The current settings are different from the default. Does this mean that the settings are still Firefly-like and should be changed to the new default; or does this mean that the defaults are still Firefly-like but the settings are actually Hammer-style ;) and thus right. Thanks, Erik. ___ ceph-users mailing list ceph-users@lists.ceph.com http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
Re: [ceph-users] What do internal_safe_to_start_threads and leveldb_compression do?
On Mon, Jun 1, 2015 at 6:53 AM, Erik Logtenberg e...@logtenberg.eu wrote: Hi, I ran a config diff, like this: ceph --admin-daemon (...).asok config diff There are the obvious things like the fsid and IP-ranges, but two settings stand out: - internal_safe_to_start_threads: true (default: false) Heh. I'm not certain exactly but this is in the depths of our common daemon startup/init code and from the name I assume it's about whether we're allowed to start threads running yet. ;) That's not something you can really change, although maybe we should move it out of a structure that's quite so user-visible. What does this do? - leveldb_compression: false (default: true) - leveldb_block/cache/write_buffer_size (all bigger than default) I take it you're running these commands on a monitor (from I think the Dumpling timeframe, or maybe even Firefly)? These are hitting specific settings in LevelDB which we tune differently for the monitor and OSD, but which were shared config options in older releases. They have their own settings in newer code. -Greg ___ ceph-users mailing list ceph-users@lists.ceph.com http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
