Oh, thank Somnath Roy !

I've set ruleset-failure-domain =osd and it works fine. There is a problem
with Crush map. When I delete a pool,
its rules are still in Crush map and it will not update the new rules
instead it will use the old rules.


2016-06-02 11:37 GMT+07:00 Somnath Roy <somnath....@sandisk.com>:

> You need to either change failure domain to osd or need at least 5 host to
> satisfy host failure domain.
>
> Since it is not satisfying failure domain , pgs are undersized and
> degraded..
>
>
>
> Thanks & Regards
>
> Somnath
>
>
>
> *From:* ceph-users [mailto:ceph-users-boun...@lists.ceph.com] *On Behalf
> Of *Khang Nguy?n Nh?t
> *Sent:* Wednesday, June 01, 2016 9:33 PM
> *To:* ceph-users@lists.ceph.com
> *Subject:* [ceph-users] Ceph Pool JERASURE issue.
>
>
>
> Hi,
>
> I have 1 cluster as pictured below:
>
>
>
> - OSD-host1 run 2 ceph-osd daemon is mounted in /var/ceph/osd0 and
>  /var/ceph/osd1.
>
> - OSD-host2 run 2 ceph-osd daemon is mounted in /var/ceph/osd2 and
>  /var/ceph/osd3.
>
> - OSD-host3 only run 1 ceph-osd daemon is mounted in the /var/ceph/osd4.
>
> - This is my myprofile:
>
>      jerasure-per-chunk-alignment = false
>
>      k = 3
>
>      m = 2
>
>      plugin = jerasure
>
>      ruleset-failure-domain = host
>
>      ruleset-root = default
>
>      technique = reed_sol_van
>
>      w = 8
>
> When I used it to create a pool
>
> CLI: ceph osd create test pool myprofile 8 8 erasure. (id test pool=62)
>
> CLI: ceph-s
>
> ​Here are the results
>
>     ///
>
>      health HEALTH_WARN
>
>             8 pgs degraded
>
>             8 pgs stuck unclean
>
>             8 pgs undersized
>
>      monmap e1: 1 mons at {mon0 = x.x.x.x: 6789/0}
>
>             election epoch 7, quorum 0 mon0
>
>      osdmap e441: 5 osds: 5 up, 5 in
>
>             flags sortbitwise
>
>       pgmap ///
>
>                    8 Active + undersized + degraded
>
>
>
> CLI: health CePH detail
>
> HEALTH_WARN 8 pgs degraded; 8 pgs stuck unclean; 8 pgs undersized
>
> 62.6 pg is stuck unclean since forever, current degraded state active + +
> undersized, last acting [1,2,2147483647,2147483647,4]
>
> 62.7 pg is stuck unclean since forever, current degraded state active + +
> undersized, last acting [2,0,2147483647,4,2147483647]
>
> 62.4 pg is stuck unclean since forever, current degraded state active + +
> undersized, last acting [3,0,4,2147483647,2147483647]
>
> 62.5 pg is stuck unclean since forever, current degraded state active + +
> undersized, last acting [0,4,2147483647,3,2147483647]
>
> 62.2 pg is stuck unclean since forever, current degraded state active + +
> undersized, last acting [1,2147483647,2147483647,4,2]
>
> 62.3 pg is stuck unclean since forever, current degraded state active + +
> undersized, last acting [2,2147483647,0,4,2147483647]
>
> 62.0 pg is stuck unclean since forever, current degraded state active + +
> undersized, last acting [0,3,2147483647,4,2147483647]
>
> 62.1 pg is stuck unclean since forever, current degraded state active + +
> undersized, last acting [4,0,3,2147483647,2147483647]
>
> is active + 62.1 pg undersized + degraded, acting
> [4,0,3,2147483647,2147483647]
>
> is active + 62.0 pg undersized + degraded, acting
> [0,3,2147483647,4,2147483647]
>
> is active + 62.3 pg undersized + degraded, acting
> [2,2147483647,0,4,2147483647]
>
> is active + 62.2 pg undersized + degraded, acting
> [1,2147483647,2147483647,4,2]
>
> is active + 62.5 pg undersized + degraded, acting
> [0,4,2147483647,3,2147483647]
>
> is active + 62.4 pg undersized + degraded, acting
> [3,0,4,2147483647,2147483647]
>
> is active + 62.7 pg undersized + degraded, acting
> [2,0,2147483647,4,2147483647]
>
> is active + 62.6 pg undersized + degraded, acting
> [1,2,2147483647,2147483647,4]
>
>
>
> This is related to reasonable ruleset-failure-domain? Can somebody please
> help me out ?
>
> Thank !
> PLEASE NOTE: The information contained in this electronic mail message is
> intended only for the use of the designated recipient(s) named above. If
> the reader of this message is not the intended recipient, you are hereby
> notified that you have received this message in error and that any review,
> dissemination, distribution, or copying of this message is strictly
> prohibited. If you have received this communication in error, please notify
> the sender by telephone or e-mail (as shown above) immediately and destroy
> any and all copies of this message in your possession (whether hard copies
> or electronically stored copies).
>
_______________________________________________
ceph-users mailing list
ceph-users@lists.ceph.com
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com

Reply via email to