You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Patrick Hunt (JIRA)" <ji...@apache.org> on 2008/10/21 02:00:44 UTC
[jira] Created: (ZOOKEEPER-199) fix log messages in persistence
code
fix log messages in persistence code
------------------------------------
Key: ZOOKEEPER-199
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-199
Project: Zookeeper
Issue Type: Bug
Affects Versions: 3.0.0
Reporter: Patrick Hunt
Assignee: Mahadev konar
Priority: Minor
Fix For: 3.0.0
there are 2 log messages during server startup that are misleading:
2008-10-20 16:36:41,135 - INFO [main:FileTxnLog$FileTxnIterator@441] - EOF excepton java.io.EOFException: Failed to read
2008-10-20 16:36:41,120 - ERROR [main:FileTxnSnapLog@114] - 2(higestZxid) >= 2(next log) for type 1
the first log should be DEBUG and should be changed to say something like eof reached in <file>, reading next file
while the second log seems to indicate an error - however the server is still starting. either this is not an error, or it is an error and it's not being handled correctly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-199) fix log messages in persistence
code
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12641347#action_12641347 ]
Hudson commented on ZOOKEEPER-199:
----------------------------------
Integrated in ZooKeeper-trunk #120 (See [http://hudson.zones.apache.org/hudson/job/ZooKeeper-trunk/120/])
. fix log messages in persistence code
> fix log messages in persistence code
> ------------------------------------
>
> Key: ZOOKEEPER-199
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-199
> Project: Zookeeper
> Issue Type: Bug
> Components: server
> Affects Versions: 3.0.0
> Reporter: Patrick Hunt
> Assignee: Mahadev konar
> Priority: Minor
> Fix For: 3.0.0
>
> Attachments: ZOOKEEPER-199.patch
>
>
> there are 2 log messages during server startup that are misleading:
> 2008-10-20 16:36:41,135 - INFO [main:FileTxnLog$FileTxnIterator@441] - EOF excepton java.io.EOFException: Failed to read
> 2008-10-20 16:36:41,120 - ERROR [main:FileTxnSnapLog@114] - 2(higestZxid) >= 2(next log) for type 1
> the first log should be DEBUG and should be changed to say something like eof reached in <file>, reading next file
> while the second log seems to indicate an error - however the server is still starting. either this is not an error, or it is an error and it's not being handled correctly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-199) fix log messages in persistence
code
Posted by "Patrick Hunt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Hunt updated ZOOKEEPER-199:
-----------------------------------
Resolution: Fixed
Hadoop Flags: [Reviewed]
Status: Resolved (was: Patch Available)
Committed revision 706512.
> fix log messages in persistence code
> ------------------------------------
>
> Key: ZOOKEEPER-199
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-199
> Project: Zookeeper
> Issue Type: Bug
> Components: server
> Affects Versions: 3.0.0
> Reporter: Patrick Hunt
> Assignee: Mahadev konar
> Priority: Minor
> Fix For: 3.0.0
>
> Attachments: ZOOKEEPER-199.patch
>
>
> there are 2 log messages during server startup that are misleading:
> 2008-10-20 16:36:41,135 - INFO [main:FileTxnLog$FileTxnIterator@441] - EOF excepton java.io.EOFException: Failed to read
> 2008-10-20 16:36:41,120 - ERROR [main:FileTxnSnapLog@114] - 2(higestZxid) >= 2(next log) for type 1
> the first log should be DEBUG and should be changed to say something like eof reached in <file>, reading next file
> while the second log seems to indicate an error - however the server is still starting. either this is not an error, or it is an error and it's not being handled correctly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-199) fix log messages in persistence
code
Posted by "Mahadev konar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mahadev konar updated ZOOKEEPER-199:
------------------------------------
Status: Patch Available (was: Open)
> fix log messages in persistence code
> ------------------------------------
>
> Key: ZOOKEEPER-199
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-199
> Project: Zookeeper
> Issue Type: Bug
> Components: server
> Affects Versions: 3.0.0
> Reporter: Patrick Hunt
> Assignee: Mahadev konar
> Priority: Minor
> Fix For: 3.0.0
>
> Attachments: ZOOKEEPER-199.patch
>
>
> there are 2 log messages during server startup that are misleading:
> 2008-10-20 16:36:41,135 - INFO [main:FileTxnLog$FileTxnIterator@441] - EOF excepton java.io.EOFException: Failed to read
> 2008-10-20 16:36:41,120 - ERROR [main:FileTxnSnapLog@114] - 2(higestZxid) >= 2(next log) for type 1
> the first log should be DEBUG and should be changed to say something like eof reached in <file>, reading next file
> while the second log seems to indicate an error - however the server is still starting. either this is not an error, or it is an error and it's not being handled correctly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-199) fix log messages in persistence
code
Posted by "Mahadev konar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mahadev konar updated ZOOKEEPER-199:
------------------------------------
Attachment: ZOOKEEPER-199.patch
this patch fixes the debug messages.
> fix log messages in persistence code
> ------------------------------------
>
> Key: ZOOKEEPER-199
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-199
> Project: Zookeeper
> Issue Type: Bug
> Components: server
> Affects Versions: 3.0.0
> Reporter: Patrick Hunt
> Assignee: Mahadev konar
> Priority: Minor
> Fix For: 3.0.0
>
> Attachments: ZOOKEEPER-199.patch
>
>
> there are 2 log messages during server startup that are misleading:
> 2008-10-20 16:36:41,135 - INFO [main:FileTxnLog$FileTxnIterator@441] - EOF excepton java.io.EOFException: Failed to read
> 2008-10-20 16:36:41,120 - ERROR [main:FileTxnSnapLog@114] - 2(higestZxid) >= 2(next log) for type 1
> the first log should be DEBUG and should be changed to say something like eof reached in <file>, reading next file
> while the second log seems to indicate an error - however the server is still starting. either this is not an error, or it is an error and it's not being handled correctly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-199) fix log messages in persistence
code
Posted by "Patrick Hunt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Hunt updated ZOOKEEPER-199:
-----------------------------------
Component/s: server
> fix log messages in persistence code
> ------------------------------------
>
> Key: ZOOKEEPER-199
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-199
> Project: Zookeeper
> Issue Type: Bug
> Components: server
> Affects Versions: 3.0.0
> Reporter: Patrick Hunt
> Assignee: Mahadev konar
> Priority: Minor
> Fix For: 3.0.0
>
>
> there are 2 log messages during server startup that are misleading:
> 2008-10-20 16:36:41,135 - INFO [main:FileTxnLog$FileTxnIterator@441] - EOF excepton java.io.EOFException: Failed to read
> 2008-10-20 16:36:41,120 - ERROR [main:FileTxnSnapLog@114] - 2(higestZxid) >= 2(next log) for type 1
> the first log should be DEBUG and should be changed to say something like eof reached in <file>, reading next file
> while the second log seems to indicate an error - however the server is still starting. either this is not an error, or it is an error and it's not being handled correctly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.