You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Attila Doroszlai (Jira)" <ji...@apache.org> on 2024/01/21 15:13:00 UTC
[jira] [Updated] (HDDS-9204) Reduce log level of PipelinePlacementPolicy failed to create pipeline message
[ https://issues.apache.org/jira/browse/HDDS-9204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Attila Doroszlai updated HDDS-9204:
-----------------------------------
Fix Version/s: 1.4.0
> Reduce log level of PipelinePlacementPolicy failed to create pipeline message
> -----------------------------------------------------------------------------
>
> Key: HDDS-9204
> URL: https://issues.apache.org/jira/browse/HDDS-9204
> Project: Apache Ozone
> Issue Type: Improvement
> Reporter: Stephen O'Donnell
> Assignee: Stephen O'Donnell
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.4.0
>
>
> Under normal circumstances, a log like this is seen frequently in the SCM log:
> {code}
> 2023-08-23 10:41:06,087 [main] WARN pipeline.PipelinePlacementPolicy (PipelinePlacementPolicy.java:filterViableNodes(166)) - Pipeline creation failed due to no sufficient healthy datanodes. Required 3. Found 2. Excluded 14.
> {code}
> This happens regularly, as the background pipeline creator thread attempts to fill all datanodes with pipelines. When all the limits have been reached the above scenario legitimately happens and prints the warning to the logs.
> We should move this message to debug along with a few others similar to it, as they are not warnings, but normal occurrences.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org