Hi, we need more information about your cluster (ceph osd tree) and the applied crush rule for this pool. What ceph version is this? Regards, Eugen Zitat von Phong Tran Thanh <tranphong079@gmail.com>:

Hi community. I' am running ceph cluster with 10 node and 180 osds, and i create an pool erasure code 4+2 with 256 PGs, but when create an pool PG too slow, and pg status stuck peering

EALTH_WARN Reduced data availability: 5 pgs inactive, 5 pgs peering [WRN] PG_AVAILABILITY: Reduced data availability: 5 pgs inactive, 5 pgs peering pg 59.6b is stuck peering for 4m, current state creating+peering, last acting [17,87,92,117,71,149] pg 59.78 is stuck peering for 4m, current state creating+peering, last acting [94,16,137,98,41,79] pg 59.86 is stuck peering for 4m, current state creating+peering, last acting [37,107,24,138,144,25]

and this is a pg query

"recovery_state": [ { "name": "Started/Primary/Peering/GetInfo", "enter_time": "2024-01-04T11:02:09.208218+0000", "requested_info_from": [ { "osd": "101(4)" } ] }, { "name": "Started/Primary/Peering", "enter_time": "2024-01-04T11:02:09.208209+0000", "past_intervals": [ { "first": "0", "last": "0", "all_participants": [], "intervals": [] } ], "probing_osds": [ "0(3)", "36(5)", "74(2)", "100(0)", "101(4)", "150(1)" ], "down_osds_we_would_probe": [], "peering_blocked_by": [] }, { "name": "Started", "enter_time": "2024-01-04T11:02:09.208161+0000" } ], "agent_state": {}

Why is the pg peering state so slow, it's affected by the network?

My network lacp with two of 10Gbps NIC

-- ---------------------------------------------------------------------------- *Tran Thanh Phong* Email: tranphong079@gmail.com Skype: tranphong079 _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io