New Jewel cluster has firefly tunables by default

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,
I noticed that when a fresh Jewel cluster is deployed, by default it has
"firefly" tunables set. Is there some reason not to set "optimal" by
default or is this a bug?


 root@caas-test01:~# ceph --version
 ceph version 10.2.3 (ecc23778eb545d8dd55e2e4735b53cc93f92e65b)
 root@caas-test01:~# ceph -s
     cluster 5c8b2c79-7a54-40ce-9203-4f4e4fad977d
      health HEALTH_ERR
             64 pgs are stuck inactive for more than 300 seconds
             64 pgs stuck inactive
             no osds
             mon.caas-test01 low disk space
      monmap e1: 1 mons at {caas-test01=167.114.246.213:6789/0}
             election epoch 3, quorum 0 caas-test01
      osdmap e1: 0 osds: 0 up, 0 in
             flags sortbitwise
       pgmap v2: 64 pgs, 1 pools, 0 bytes data, 0 objects
             0 kB used, 0 kB / 0 kB avail
                   64 creating
 root@caas-test01:~# ceph osd crush show-tunables
 {
     "choose_local_tries": 0,
     "choose_local_fallback_tries": 0,
     "choose_total_tries": 50,
     "chooseleaf_descend_once": 1,
     "chooseleaf_vary_r": 1,
     "chooseleaf_stable": 0,
     "straw_calc_version": 1,
     "allowed_bucket_algs": 22,
     "profile": "firefly",
     "optimal_tunables": 0,
     "legacy_tunables": 0,
     "minimum_required_version": "firefly",
     "require_feature_tunables": 1,
     "require_feature_tunables2": 1,
     "has_v2_rules": 0,
     "require_feature_tunables3": 1,
     "has_v3_rules": 0,
     "has_v4_buckets": 0,
     "require_feature_tunables5": 0,
     "has_v5_rules": 0
 }


-- 
Tomasz Kuzemko
tomasz.kuzemko@xxxxxxxxxxxx

Attachment: signature.asc
Description: OpenPGP digital signature


[Index of Archives]     [CEPH Users]     [Ceph Large]     [Information on CEPH]     [Linux BTRFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]
  Powered by Linux