[
https://issues.apache.org/jira/browse/HDDS-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16781078#comment-16781078
]
Anu Engineer commented on HDDS-1142:
------------------------------------
Not sure how this can happen, very strange. Do we have an issue with Log4j or
something? Anyways, moving to next milestone for now.
> Inconsistency in Ozone log rollovers
> ------------------------------------
>
> Key: HDDS-1142
> URL: https://issues.apache.org/jira/browse/HDDS-1142
> Project: Hadoop Distributed Data Store
> Issue Type: Improvement
> Affects Versions: 0.4.0
> Reporter: Shashikant Banerjee
> Priority: Major
> Fix For: 0.4.0
>
>
> HW15685:nodes-ozone-logs-1550481382 sbanerjee$ head
> ozone-log-1550481382-172.27.76.72/root/hadoop_trunk/ozone-0.4.0-SNAPSHOT/logs/ozone.log.2019-02-15
> 2019-02-17 00:00:17,817 [Datanode State Machine Thread - 0] DEBUG
> (DatanodeStateMachine.java:176) - Executing cycle Number : 4634
> 2019-02-17 00:00:47,819 [Datanode State Machine Thread - 0] DEBUG
> (DatanodeStateMachine.java:176) - Executing cycle Number : 4635
> 2019-02-17 00:00:57,662 [Datanode ReportManager Thread - 0] DEBUG
> (ContainerSet.java:192) - Starting container report iteration.
> 2019-02-17 00:00:57,887 [BlockDeletingService#7] DEBUG
> (TopNOrderedContainerDeletionChoosingPolicy.java:79) - Stop looking for next
> container, there is no pending deletion block contained in remaining
> containers.
>
> The ozone.log.2019-02-15 file contains logs for 2019-02-17.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
