[ 
https://issues.apache.org/jira/browse/HDFS-14270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16783749#comment-16783749
 ] 

Hadoop QA commented on HDFS-14270:
----------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red}  0m  6s{color} 
| {color:red} HDFS-14270 does not apply to trunk. Rebase required? Wrong 
Branch? See https://wiki.apache.org/hadoop/HowToContribute for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HDFS-14270 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12961044/HDFS-14270.002.patch |
| Console output | 
https://builds.apache.org/job/PreCommit-HDFS-Build/26397/console |
| Powered by | Apache Yetus 0.8.0   http://yetus.apache.org |


This message was automatically generated.



> [SBN Read] StateId and TrasactionId not present in Trace level logging
> ----------------------------------------------------------------------
>
>                 Key: HDFS-14270
>                 URL: https://issues.apache.org/jira/browse/HDFS-14270
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: namenode
>            Reporter: Shweta
>            Assignee: Shweta
>            Priority: Trivial
>         Attachments: HDFS-14270.001.patch, HDFS-14270.002.patch
>
>
> While running the command "hdfs --loglevel TRACE dfs -ls /" it was seen that 
> stateId and TransactionId do not appear in the logs. 
How does one see the 
> stateId and TransactionId in the logs? Is there a different approach?
> CC: [~jojochuang], [~csun], [~shv]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to