You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Li Cheng (Jira)" <ji...@apache.org> on 2019/12/18 14:16:00 UTC
[jira] [Commented] (HDDS-2756) Handle pipeline creation failure in
different way when it exceeds pipeline limit
[ https://issues.apache.org/jira/browse/HDDS-2756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16999201#comment-16999201 ]
Li Cheng commented on HDDS-2756:
--------------------------------
Also polish the wording for logging and exception messages.
> Handle pipeline creation failure in different way when it exceeds pipeline limit
> --------------------------------------------------------------------------------
>
> Key: HDDS-2756
> URL: https://issues.apache.org/jira/browse/HDDS-2756
> Project: Hadoop Distributed Data Store
> Issue Type: Sub-task
> Reporter: Li Cheng
> Assignee: Li Cheng
> Priority: Minor
>
> In current codes, pipeline creation failure will print out entire error trace when it exceeds pipeline number limit., which is very like false alarms. We should limit printing this type of trace and don't consider it as an error.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-issues-help@hadoop.apache.org