You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Ethan Rose (Jira)" <ji...@apache.org> on 2021/10/20 20:39:11 UTC
[jira] [Updated] (HDDS-1755) getContainerWithPipeline should log
the container ID in case of failure
[ https://issues.apache.org/jira/browse/HDDS-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ethan Rose updated HDDS-1755:
-----------------------------
Target Version/s: 1.3.0 (was: 1.2.0)
I am managing the 1.2.0 release and we currently have more than 600 issues targeted for 1.2.0. I am moving the target field to 1.3.0.
If you are actively working on this jira and believe this should be targeted for the 1.2.0 release, Please reach out to me via Apache email or Slack.
> getContainerWithPipeline should log the container ID in case of failure
> -----------------------------------------------------------------------
>
> Key: HDDS-1755
> URL: https://issues.apache.org/jira/browse/HDDS-1755
> Project: Apache Ozone
> Issue Type: Bug
> Components: SCM
> Affects Versions: 0.4.0
> Reporter: Mukul Kumar Singh
> Assignee: Nandakumar
> Priority: Minor
> Labels: MiniOzoneChaosCluster
>
> getContainerWithPipeline should log the container ID in scm logs for easy debugging.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org