It sucks that its so hard to set/view active settings, this should be a lot
simpler in my opinion
On Tue, Apr 23, 2019 at 1:58 PM solarflow99 wrote:
> Thanks, but does this not work on Luminous maybe? I am on the mon hosts
> trying this:
>
>
> # ceph config set osd osd_recovery_max_active 4
> I
On 4/25/19 11:33 AM, Francois Scheurer wrote:
Hello Amardeep
We are trying the same as you on luminous.
s3cmd --access_key xxx --secret_key xxx --host-bucket '%(bucket)s.s3.xxx.ch'
--host s3.xxx.ch --signature-v2 --no-preserve --server-side-encryption \
--server-side-encryption-kms-idhttps://
If you are just synching to the outside pool, the three hosts may end up
latching on to different outside servers as their definitive sources.
You might want to make one of the three a higher priority source to the
other two and possibly just have it use the outside sources as sync.
Also for
Hello Amardeep
We are trying the same as you on luminous.
s3cmd --access_key xxx --secret_key xxx --host-bucket '%(bucket)s.s3.xxx.ch'
--host s3.xxx.ch --signature-v2 --no-preserve --server-side-encryption \
--server-side-encryption-kms-id
https://barbican.service.xxx.ch/v1/secrets/ffa60094-
+1 to Janne's suggestion. Also, how many time sources are you using? More
tend to be better and by default chrony has a pretty low limit on the
number of sources if you're using a pool (3 or 4 i think?). You can adjust
it by adding maxsources to the pool line.
pool pool.ntp.org iburst maxsources 8
Den tors 25 apr. 2019 kl 13:00 skrev huang jun :
> mj 于2019年4月25日周四 下午6:34写道：
> >
> > Hi all,
> >
> > On our three-node cluster, we have setup chrony for time sync, and even
> > though chrony reports that it is synced to ntp time, at the same time
> > ceph occasionally reports time skews that can
mj 于2019年4月25日周四 下午6:34写道：
>
> Hi all,
>
> On our three-node cluster, we have setup chrony for time sync, and even
> though chrony reports that it is synced to ntp time, at the same time
> ceph occasionally reports time skews that can last several hours.
>
> See for example:
>
> > root@ceph2:~# ce
Hi all,
On our three-node cluster, we have setup chrony for time sync, and even
though chrony reports that it is synced to ntp time, at the same time
ceph occasionally reports time skews that can last several hours.
See for example:
root@ceph2:~# ceph -v
ceph version 12.2.10 (fc2b1783e3727b
