[
https://issues.apache.org/jira/browse/HDDS-12234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wei-Chiu Chuang updated HDDS-12234:
-----------------------------------
Description:
Found these log messages in OM and it doesn't help me troubleshoot the problem.
{noformat}
2025-02-05 20:31:46,560 ERROR
[qtp954207047-86]-org.apache.hadoop.ozone.om.OzoneManager: No leader found
2025-02-05 20:32:46,559 ERROR
[qtp954207047-82]-org.apache.hadoop.ozone.om.OzoneManager: No leader found
2025-02-05 20:33:46,566 ERROR
[qtp954207047-193]-org.apache.hadoop.ozone.om.OzoneManager: No leader found
2025-02-05 20:34:46,560 ERROR
[qtp954207047-86]-org.apache.hadoop.ozone.om.OzoneManager: No leader found
2025-02-05 20:35:46,565 ERROR
[qtp954207047-84]-org.apache.hadoop.ozone.om.OzoneManager: No leader found
2025-02-05 20:36:46,562 ERROR
[qtp954207047-193]-org.apache.hadoop.ozone.om.OzoneManager: No leader found
2025-02-05 20:37:46,557 ERROR
[qtp954207047-86]-org.apache.hadoop.ozone.om.OzoneManager: No leader found
{noformat}
These error logs are emitted when JMX end point is accessed.
To improve the error log, consider updating it to "There are no leader among
the Ozone Manager servers. If this message persists, the service may be down.
Possible cause: only one OM is up, or other OMs are unable to respond to Ratis
leader vote messages"
was:
Found these log messages in OM and it doesn't help me troubleshoot the problem.
{noformat}
2025-02-05 20:31:46,560 ERROR
[qtp954207047-86]-org.apache.hadoop.ozone.om.OzoneManager: No leader found
2025-02-05 20:32:46,559 ERROR
[qtp954207047-82]-org.apache.hadoop.ozone.om.OzoneManager: No leader found
2025-02-05 20:33:46,566 ERROR
[qtp954207047-193]-org.apache.hadoop.ozone.om.OzoneManager: No leader found
2025-02-05 20:34:46,560 ERROR
[qtp954207047-86]-org.apache.hadoop.ozone.om.OzoneManager: No leader found
2025-02-05 20:35:46,565 ERROR
[qtp954207047-84]-org.apache.hadoop.ozone.om.OzoneManager: No leader found
2025-02-05 20:36:46,562 ERROR
[qtp954207047-193]-org.apache.hadoop.ozone.om.OzoneManager: No leader found
2025-02-05 20:37:46,557 ERROR
[qtp954207047-86]-org.apache.hadoop.ozone.om.OzoneManager: No leader found
{noformat}
These error logs are emitted when JMX end point is accessed.
To improve the error log, consider updating it to "There are no leader among
the Ozone Manager servers. The service may be down.Possible cause: only one OM
is up, or other OMs are unable to respond to Ratis leader vote messages"
> Improve error "No leader found"
> -------------------------------
>
> Key: HDDS-12234
> URL: https://issues.apache.org/jira/browse/HDDS-12234
> Project: Apache Ozone
> Issue Type: Improvement
> Reporter: Wei-Chiu Chuang
> Priority: Minor
>
> Found these log messages in OM and it doesn't help me troubleshoot the
> problem.
> {noformat}
> 2025-02-05 20:31:46,560 ERROR
> [qtp954207047-86]-org.apache.hadoop.ozone.om.OzoneManager: No leader found
> 2025-02-05 20:32:46,559 ERROR
> [qtp954207047-82]-org.apache.hadoop.ozone.om.OzoneManager: No leader found
> 2025-02-05 20:33:46,566 ERROR
> [qtp954207047-193]-org.apache.hadoop.ozone.om.OzoneManager: No leader found
> 2025-02-05 20:34:46,560 ERROR
> [qtp954207047-86]-org.apache.hadoop.ozone.om.OzoneManager: No leader found
> 2025-02-05 20:35:46,565 ERROR
> [qtp954207047-84]-org.apache.hadoop.ozone.om.OzoneManager: No leader found
> 2025-02-05 20:36:46,562 ERROR
> [qtp954207047-193]-org.apache.hadoop.ozone.om.OzoneManager: No leader found
> 2025-02-05 20:37:46,557 ERROR
> [qtp954207047-86]-org.apache.hadoop.ozone.om.OzoneManager: No leader found
> {noformat}
> These error logs are emitted when JMX end point is accessed.
> To improve the error log, consider updating it to "There are no leader among
> the Ozone Manager servers. If this message persists, the service may be down.
> Possible cause: only one OM is up, or other OMs are unable to respond to
> Ratis leader vote messages"
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
