[ceph-users] Re: Upgraded 16.2.14 to 16.2.15

2024-03-05 Thread Eugen Block
Thanks for chiming in, Adam. Zitat von Adam King : There was a bug with this that was fixed by https://github.com/ceph/ceph/pull/52122 (which also specifically added an integration test for this case). It looks like it's missing a reef and quincy backport though unfortunately. I'll try to open

[ceph-users] Re: Upgraded 16.2.14 to 16.2.15

2024-03-05 Thread Adam King
There was a bug with this that was fixed by https://github.com/ceph/ceph/pull/52122 (which also specifically added an integration test for this case). It looks like it's missing a reef and quincy backport though unfortunately. I'll try to open one for both. On Tue, Mar 5, 2024 at 8:26 AM Eugen

[ceph-users] Re: Upgraded 16.2.14 to 16.2.15

2024-03-05 Thread Eugen Block
It seems to be an issue with the service type (in this case "mon"), it's not entirely "broken", with the node-exporter it works: quincy-1:~ # cat node-exporter.yaml service_type: node-exporter service_name: node-exporter placement:  host_pattern: '*' extra_entrypoint_args:  -

[ceph-users] Re: Upgraded 16.2.14 to 16.2.15

2024-03-05 Thread Eugen Block
Oh, you're right. I just checked on Quincy as well at it failed with the same error message. For pacific it still works. I'll check for existing tracker issues. Zitat von Robert Sander : Hi, On 3/5/24 08:57, Eugen Block wrote: extra_entrypoint_args:   -

[ceph-users] Re: Upgraded 16.2.14 to 16.2.15

2024-03-05 Thread Robert Sander
Hi, On 3/5/24 08:57, Eugen Block wrote: extra_entrypoint_args:   - '--mon-rocksdb-options=write_buffer_size=33554432,compression=kLZ4Compression,level_compaction_dynamic_level_bytes=true,bottommost_compression=kLZ4HCCompression,max_background_jobs=4,max_subcompactions=2' When I try this on

[ceph-users] Re: Upgraded 16.2.14 to 16.2.15

2024-03-05 Thread Zakhar Kirpichenko
Well, that option could be included in new mon configs generated during mon upgrades. But it isn't being used, a minimal config is written instead. I.e. it seems that the configuration option is useless for all intents and purposes, as it doesn't seem to be taken into account at any stage of a

[ceph-users] Re: Upgraded 16.2.14 to 16.2.15

2024-03-05 Thread Eugen Block
Hi, I also added it to the cluster config with "ceph config set mon mon_rocksdb_options", but it seems that this option doesn't have any effect at all. that's because it's an option that has to be present *during* mon startup, not *after* the startup when it can read the config store.

[ceph-users] Re: Upgraded 16.2.14 to 16.2.15

2024-03-05 Thread Zakhar Kirpichenko
Hi Eugen, It is correct that I manually added the configuration, but not to the unit.run but rather to each mon's config (i.e. /var/lib/ceph/FSID/mon.*/config). I also added it to the cluster config with "ceph config set mon mon_rocksdb_options", but it seems that this option doesn't have any

[ceph-users] Re: Upgraded 16.2.14 to 16.2.15

2024-03-04 Thread Eugen Block
Hi, 1. RocksDB options, which I provided to each mon via their configuration files, got overwritten during mon redeployment and I had to re-add mon_rocksdb_options back. IIRC, you didn't use the extra_entrypoint_args for that option but added it directly to the container unit.run file. So