Why RGWAsyncRadosProcessor threads time out on secondary RGW in multisite configuration ?

Solution Verified - Updated -

Issue

  • Why data sync is not happening in multisite configuration ?
  • Why secondary zone rgw logs reporting RGWAsyncRadosProcessor::m_tp thread timed out errors ?

    # tailf /var/log/ceph/ceph-rgw-cephc3-rgwb.log | grep  RGWAsyncRadosProcessor
    2018-06-02 02:33:47.304520 7babadadaf700  1 heartbeat_map is_healthy 'RGWAsyncRadosProcessor::m_tp thread 0x7fbaddaad700' had timed out after 600
    2018-06-02 02:33:52.304594 7babadadaf700  1 heartbeat_map is_healthy 'RGWAsyncRadosProcessor::m_tp thread 0x7fbaddaad700' had timed out after 600
    2018-06-02 02:33:57.304664 7babadadaf700  1 heartbeat_map is_healthy 'RGWAsyncRadosProcessor::m_tp thread 0x7fbaddaad700' had timed out after 600
    2018-06-02 02:33:57.304737 7babadadaf700  1 heartbeat_map is_healthy 'RGWAsyncRadosProcessor::m_tp thread 0x7fbaddaad700' had timed out after 600
    2018-06-02 02:33:57.304780 7babadadaf700  1 heartbeat_map is_healthy 'RGWAsyncRadosProcessor::m_tp thread 0x7fbaddaad700' had timed out after 600
    

Environment

  • Red Hat Enterprise Linux 7.x
  • Red Hat Ceph Storage 3.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In