[jira] [Commented] (HBASE-7122) Proper warning message when opening a log file with no entries (idle cluster)
[
https://issues.apache.org/jira/browse/HBASE-7122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13658919#comment-13658919
]
Hudson commented on HBASE-7122:
---
Integrated in HBase-0.94-security #141 (See
[https://builds.apache.org/job/HBase-0.94-security/141/])
HBASE-7122 Proper warning message when opening a log file with no entries
(idle cluster) (Himanshu) (Revision 1479037)
Result = FAILURE
larsh :
Files :
*
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/replication/regionserver/ReplicationSource.java
Proper warning message when opening a log file with no entries (idle cluster)
-
Key: HBASE-7122
URL: https://issues.apache.org/jira/browse/HBASE-7122
Project: HBase
Issue Type: Bug
Components: Replication
Affects Versions: 0.94.2
Reporter: Himanshu Vashishtha
Assignee: Himanshu Vashishtha
Fix For: 0.98.0, 0.94.8, 0.95.1
Attachments: HBase-7122-94.patch, HBase-7122-94-v2.patch,
HBase-7122-95.patch, HBase-7122-95-v2.patch, HBase-7122-95-v3.patch,
HBase-7122-95-v4.patch, HBase-7122.patch, HBASE-7122.v2.patch
In case the cluster is idle and the log has rolled (offset to 0),
replicationSource tries to open the log and gets an EOF exception. This gets
printed after every 10 sec until an entry is inserted in it.
{code}
2012-11-07 15:47:40,924 DEBUG regionserver.ReplicationSource
(ReplicationSource.java:openReader(487)) - Opening log for replication
c0315.hal.cloudera.com%2C40020%2C1352324202860.1352327804874 at 0
2012-11-07 15:47:40,926 WARN regionserver.ReplicationSource
(ReplicationSource.java:openReader(543)) - 1 Got:
java.io.EOFException
at java.io.DataInputStream.readFully(DataInputStream.java:180)
at java.io.DataInputStream.readFully(DataInputStream.java:152)
at org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1508)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1486)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1475)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1470)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader$WALReader.init(SequenceFileLogReader.java:55)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader.init(SequenceFileLogReader.java:175)
at
org.apache.hadoop.hbase.regionserver.wal.HLog.getReader(HLog.java:716)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.openReader(ReplicationSource.java:491)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.run(ReplicationSource.java:290)
2012-11-07 15:47:40,927 WARN regionserver.ReplicationSource
(ReplicationSource.java:openReader(547)) - Waited too long for this file,
considering dumping
2012-11-07 15:47:40,927 DEBUG regionserver.ReplicationSource
(ReplicationSource.java:sleepForRetries(562)) - Unable to open a reader,
sleeping 1000 times 10
{code}
We should reduce the log spewing in this case (or some informative message,
based on the offset).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-7122) Proper warning message when opening a log file with no entries (idle cluster)
[
https://issues.apache.org/jira/browse/HBASE-7122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13650585#comment-13650585
]
Hudson commented on HBASE-7122:
---
Integrated in HBase-0.94 #974 (See
[https://builds.apache.org/job/HBase-0.94/974/])
HBASE-7122 Proper warning message when opening a log file with no entries
(idle cluster) (Himanshu) (Revision 1479037)
Result = SUCCESS
larsh :
Files :
*
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/replication/regionserver/ReplicationSource.java
Proper warning message when opening a log file with no entries (idle cluster)
-
Key: HBASE-7122
URL: https://issues.apache.org/jira/browse/HBASE-7122
Project: HBase
Issue Type: Bug
Components: Replication
Affects Versions: 0.94.2
Reporter: Himanshu Vashishtha
Assignee: Himanshu Vashishtha
Fix For: 0.98.0, 0.94.8, 0.95.1
Attachments: HBase-7122-94.patch, HBase-7122-94-v2.patch,
HBase-7122-95.patch, HBase-7122-95-v2.patch, HBase-7122-95-v3.patch,
HBase-7122-95-v4.patch, HBase-7122.patch, HBASE-7122.v2.patch
In case the cluster is idle and the log has rolled (offset to 0),
replicationSource tries to open the log and gets an EOF exception. This gets
printed after every 10 sec until an entry is inserted in it.
{code}
2012-11-07 15:47:40,924 DEBUG regionserver.ReplicationSource
(ReplicationSource.java:openReader(487)) - Opening log for replication
c0315.hal.cloudera.com%2C40020%2C1352324202860.1352327804874 at 0
2012-11-07 15:47:40,926 WARN regionserver.ReplicationSource
(ReplicationSource.java:openReader(543)) - 1 Got:
java.io.EOFException
at java.io.DataInputStream.readFully(DataInputStream.java:180)
at java.io.DataInputStream.readFully(DataInputStream.java:152)
at org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1508)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1486)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1475)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1470)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader$WALReader.init(SequenceFileLogReader.java:55)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader.init(SequenceFileLogReader.java:175)
at
org.apache.hadoop.hbase.regionserver.wal.HLog.getReader(HLog.java:716)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.openReader(ReplicationSource.java:491)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.run(ReplicationSource.java:290)
2012-11-07 15:47:40,927 WARN regionserver.ReplicationSource
(ReplicationSource.java:openReader(547)) - Waited too long for this file,
considering dumping
2012-11-07 15:47:40,927 DEBUG regionserver.ReplicationSource
(ReplicationSource.java:sleepForRetries(562)) - Unable to open a reader,
sleeping 1000 times 10
{code}
We should reduce the log spewing in this case (or some informative message,
based on the offset).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-7122) Proper warning message when opening a log file with no entries (idle cluster)
[
https://issues.apache.org/jira/browse/HBASE-7122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13649002#comment-13649002
]
Lars Hofhansl commented on HBASE-7122:
--
Committed to 0.94 as well.
Proper warning message when opening a log file with no entries (idle cluster)
-
Key: HBASE-7122
URL: https://issues.apache.org/jira/browse/HBASE-7122
Project: HBase
Issue Type: Bug
Components: Replication
Affects Versions: 0.94.2
Reporter: Himanshu Vashishtha
Assignee: Himanshu Vashishtha
Fix For: 0.98.0, 0.94.8, 0.95.1
Attachments: HBase-7122-94.patch, HBase-7122-94-v2.patch,
HBase-7122-95.patch, HBase-7122-95-v2.patch, HBase-7122-95-v3.patch,
HBase-7122-95-v4.patch, HBase-7122.patch, HBASE-7122.v2.patch
In case the cluster is idle and the log has rolled (offset to 0),
replicationSource tries to open the log and gets an EOF exception. This gets
printed after every 10 sec until an entry is inserted in it.
{code}
2012-11-07 15:47:40,924 DEBUG regionserver.ReplicationSource
(ReplicationSource.java:openReader(487)) - Opening log for replication
c0315.hal.cloudera.com%2C40020%2C1352324202860.1352327804874 at 0
2012-11-07 15:47:40,926 WARN regionserver.ReplicationSource
(ReplicationSource.java:openReader(543)) - 1 Got:
java.io.EOFException
at java.io.DataInputStream.readFully(DataInputStream.java:180)
at java.io.DataInputStream.readFully(DataInputStream.java:152)
at org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1508)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1486)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1475)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1470)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader$WALReader.init(SequenceFileLogReader.java:55)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader.init(SequenceFileLogReader.java:175)
at
org.apache.hadoop.hbase.regionserver.wal.HLog.getReader(HLog.java:716)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.openReader(ReplicationSource.java:491)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.run(ReplicationSource.java:290)
2012-11-07 15:47:40,927 WARN regionserver.ReplicationSource
(ReplicationSource.java:openReader(547)) - Waited too long for this file,
considering dumping
2012-11-07 15:47:40,927 DEBUG regionserver.ReplicationSource
(ReplicationSource.java:sleepForRetries(562)) - Unable to open a reader,
sleeping 1000 times 10
{code}
We should reduce the log spewing in this case (or some informative message,
based on the offset).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-7122) Proper warning message when opening a log file with no entries (idle cluster)
[
https://issues.apache.org/jira/browse/HBASE-7122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13648207#comment-13648207
]
Lars Hofhansl commented on HBASE-7122:
--
Looks good. Will commit to 0.94 tomorrow if I hear no objections.
Proper warning message when opening a log file with no entries (idle cluster)
-
Key: HBASE-7122
URL: https://issues.apache.org/jira/browse/HBASE-7122
Project: HBase
Issue Type: Bug
Components: Replication
Affects Versions: 0.94.2
Reporter: Himanshu Vashishtha
Assignee: Himanshu Vashishtha
Fix For: 0.98.0, 0.94.8, 0.95.1
Attachments: HBase-7122-94.patch, HBase-7122-94-v2.patch,
HBase-7122-95.patch, HBase-7122-95-v2.patch, HBase-7122-95-v3.patch,
HBase-7122-95-v4.patch, HBase-7122.patch, HBASE-7122.v2.patch
In case the cluster is idle and the log has rolled (offset to 0),
replicationSource tries to open the log and gets an EOF exception. This gets
printed after every 10 sec until an entry is inserted in it.
{code}
2012-11-07 15:47:40,924 DEBUG regionserver.ReplicationSource
(ReplicationSource.java:openReader(487)) - Opening log for replication
c0315.hal.cloudera.com%2C40020%2C1352324202860.1352327804874 at 0
2012-11-07 15:47:40,926 WARN regionserver.ReplicationSource
(ReplicationSource.java:openReader(543)) - 1 Got:
java.io.EOFException
at java.io.DataInputStream.readFully(DataInputStream.java:180)
at java.io.DataInputStream.readFully(DataInputStream.java:152)
at org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1508)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1486)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1475)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1470)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader$WALReader.init(SequenceFileLogReader.java:55)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader.init(SequenceFileLogReader.java:175)
at
org.apache.hadoop.hbase.regionserver.wal.HLog.getReader(HLog.java:716)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.openReader(ReplicationSource.java:491)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.run(ReplicationSource.java:290)
2012-11-07 15:47:40,927 WARN regionserver.ReplicationSource
(ReplicationSource.java:openReader(547)) - Waited too long for this file,
considering dumping
2012-11-07 15:47:40,927 DEBUG regionserver.ReplicationSource
(ReplicationSource.java:sleepForRetries(562)) - Unable to open a reader,
sleeping 1000 times 10
{code}
We should reduce the log spewing in this case (or some informative message,
based on the offset).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-7122) Proper warning message when opening a log file with no entries (idle cluster)
[
https://issues.apache.org/jira/browse/HBASE-7122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13645558#comment-13645558
]
Himanshu Vashishtha commented on HBASE-7122:
Ok, will upload a 0.94 patch today :)
Proper warning message when opening a log file with no entries (idle cluster)
-
Key: HBASE-7122
URL: https://issues.apache.org/jira/browse/HBASE-7122
Project: HBase
Issue Type: Bug
Components: Replication
Affects Versions: 0.94.2
Reporter: Himanshu Vashishtha
Assignee: Himanshu Vashishtha
Fix For: 0.98.0, 0.95.1
Attachments: HBase-7122-94.patch, HBase-7122-95.patch,
HBase-7122-95-v2.patch, HBase-7122-95-v3.patch, HBase-7122-95-v4.patch,
HBase-7122.patch, HBASE-7122.v2.patch
In case the cluster is idle and the log has rolled (offset to 0),
replicationSource tries to open the log and gets an EOF exception. This gets
printed after every 10 sec until an entry is inserted in it.
{code}
2012-11-07 15:47:40,924 DEBUG regionserver.ReplicationSource
(ReplicationSource.java:openReader(487)) - Opening log for replication
c0315.hal.cloudera.com%2C40020%2C1352324202860.1352327804874 at 0
2012-11-07 15:47:40,926 WARN regionserver.ReplicationSource
(ReplicationSource.java:openReader(543)) - 1 Got:
java.io.EOFException
at java.io.DataInputStream.readFully(DataInputStream.java:180)
at java.io.DataInputStream.readFully(DataInputStream.java:152)
at org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1508)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1486)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1475)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1470)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader$WALReader.init(SequenceFileLogReader.java:55)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader.init(SequenceFileLogReader.java:175)
at
org.apache.hadoop.hbase.regionserver.wal.HLog.getReader(HLog.java:716)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.openReader(ReplicationSource.java:491)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.run(ReplicationSource.java:290)
2012-11-07 15:47:40,927 WARN regionserver.ReplicationSource
(ReplicationSource.java:openReader(547)) - Waited too long for this file,
considering dumping
2012-11-07 15:47:40,927 DEBUG regionserver.ReplicationSource
(ReplicationSource.java:sleepForRetries(562)) - Unable to open a reader,
sleeping 1000 times 10
{code}
We should reduce the log spewing in this case (or some informative message,
based on the offset).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-7122) Proper warning message when opening a log file with no entries (idle cluster)
[
https://issues.apache.org/jira/browse/HBASE-7122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13645174#comment-13645174
]
Lars Hofhansl commented on HBASE-7122:
--
What happened to 0.94?
Proper warning message when opening a log file with no entries (idle cluster)
-
Key: HBASE-7122
URL: https://issues.apache.org/jira/browse/HBASE-7122
Project: HBase
Issue Type: Bug
Components: Replication
Affects Versions: 0.94.2
Reporter: Himanshu Vashishtha
Assignee: Himanshu Vashishtha
Fix For: 0.98.0, 0.95.1
Attachments: HBase-7122-94.patch, HBase-7122-95.patch,
HBase-7122-95-v2.patch, HBase-7122-95-v3.patch, HBase-7122-95-v4.patch,
HBase-7122.patch, HBASE-7122.v2.patch
In case the cluster is idle and the log has rolled (offset to 0),
replicationSource tries to open the log and gets an EOF exception. This gets
printed after every 10 sec until an entry is inserted in it.
{code}
2012-11-07 15:47:40,924 DEBUG regionserver.ReplicationSource
(ReplicationSource.java:openReader(487)) - Opening log for replication
c0315.hal.cloudera.com%2C40020%2C1352324202860.1352327804874 at 0
2012-11-07 15:47:40,926 WARN regionserver.ReplicationSource
(ReplicationSource.java:openReader(543)) - 1 Got:
java.io.EOFException
at java.io.DataInputStream.readFully(DataInputStream.java:180)
at java.io.DataInputStream.readFully(DataInputStream.java:152)
at org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1508)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1486)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1475)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1470)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader$WALReader.init(SequenceFileLogReader.java:55)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader.init(SequenceFileLogReader.java:175)
at
org.apache.hadoop.hbase.regionserver.wal.HLog.getReader(HLog.java:716)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.openReader(ReplicationSource.java:491)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.run(ReplicationSource.java:290)
2012-11-07 15:47:40,927 WARN regionserver.ReplicationSource
(ReplicationSource.java:openReader(547)) - Waited too long for this file,
considering dumping
2012-11-07 15:47:40,927 DEBUG regionserver.ReplicationSource
(ReplicationSource.java:sleepForRetries(562)) - Unable to open a reader,
sleeping 1000 times 10
{code}
We should reduce the log spewing in this case (or some informative message,
based on the offset).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-7122) Proper warning message when opening a log file with no entries (idle cluster)
[
https://issues.apache.org/jira/browse/HBASE-7122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13640233#comment-13640233
]
Hudson commented on HBASE-7122:
---
Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #508 (See
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/508/])
HBASE-7122 Proper warning message when opening a log file with no entries
(idle cluster) (Revision 1471255)
Result = FAILURE
stack :
Files :
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/ReplicationSource.java
Proper warning message when opening a log file with no entries (idle cluster)
-
Key: HBASE-7122
URL: https://issues.apache.org/jira/browse/HBASE-7122
Project: HBase
Issue Type: Bug
Components: Replication
Affects Versions: 0.94.2
Reporter: Himanshu Vashishtha
Assignee: Himanshu Vashishtha
Fix For: 0.95.1
Attachments: HBase-7122-94.patch, HBase-7122-95.patch,
HBase-7122-95-v2.patch, HBase-7122-95-v3.patch, HBase-7122-95-v4.patch,
HBase-7122.patch, HBASE-7122.v2.patch
In case the cluster is idle and the log has rolled (offset to 0),
replicationSource tries to open the log and gets an EOF exception. This gets
printed after every 10 sec until an entry is inserted in it.
{code}
2012-11-07 15:47:40,924 DEBUG regionserver.ReplicationSource
(ReplicationSource.java:openReader(487)) - Opening log for replication
c0315.hal.cloudera.com%2C40020%2C1352324202860.1352327804874 at 0
2012-11-07 15:47:40,926 WARN regionserver.ReplicationSource
(ReplicationSource.java:openReader(543)) - 1 Got:
java.io.EOFException
at java.io.DataInputStream.readFully(DataInputStream.java:180)
at java.io.DataInputStream.readFully(DataInputStream.java:152)
at org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1508)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1486)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1475)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1470)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader$WALReader.init(SequenceFileLogReader.java:55)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader.init(SequenceFileLogReader.java:175)
at
org.apache.hadoop.hbase.regionserver.wal.HLog.getReader(HLog.java:716)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.openReader(ReplicationSource.java:491)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.run(ReplicationSource.java:290)
2012-11-07 15:47:40,927 WARN regionserver.ReplicationSource
(ReplicationSource.java:openReader(547)) - Waited too long for this file,
considering dumping
2012-11-07 15:47:40,927 DEBUG regionserver.ReplicationSource
(ReplicationSource.java:sleepForRetries(562)) - Unable to open a reader,
sleeping 1000 times 10
{code}
We should reduce the log spewing in this case (or some informative message,
based on the offset).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-7122) Proper warning message when opening a log file with no entries (idle cluster)
[
https://issues.apache.org/jira/browse/HBASE-7122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13640283#comment-13640283
]
Hudson commented on HBASE-7122:
---
Integrated in hbase-0.95-on-hadoop2 #78 (See
[https://builds.apache.org/job/hbase-0.95-on-hadoop2/78/])
HBASE-7122 Proper warning message when opening a log file with no entries
(idle cluster) (Revision 1471256)
Result = FAILURE
stack :
Files :
*
/hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/ReplicationSource.java
Proper warning message when opening a log file with no entries (idle cluster)
-
Key: HBASE-7122
URL: https://issues.apache.org/jira/browse/HBASE-7122
Project: HBase
Issue Type: Bug
Components: Replication
Affects Versions: 0.94.2
Reporter: Himanshu Vashishtha
Assignee: Himanshu Vashishtha
Fix For: 0.95.1
Attachments: HBase-7122-94.patch, HBase-7122-95.patch,
HBase-7122-95-v2.patch, HBase-7122-95-v3.patch, HBase-7122-95-v4.patch,
HBase-7122.patch, HBASE-7122.v2.patch
In case the cluster is idle and the log has rolled (offset to 0),
replicationSource tries to open the log and gets an EOF exception. This gets
printed after every 10 sec until an entry is inserted in it.
{code}
2012-11-07 15:47:40,924 DEBUG regionserver.ReplicationSource
(ReplicationSource.java:openReader(487)) - Opening log for replication
c0315.hal.cloudera.com%2C40020%2C1352324202860.1352327804874 at 0
2012-11-07 15:47:40,926 WARN regionserver.ReplicationSource
(ReplicationSource.java:openReader(543)) - 1 Got:
java.io.EOFException
at java.io.DataInputStream.readFully(DataInputStream.java:180)
at java.io.DataInputStream.readFully(DataInputStream.java:152)
at org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1508)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1486)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1475)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1470)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader$WALReader.init(SequenceFileLogReader.java:55)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader.init(SequenceFileLogReader.java:175)
at
org.apache.hadoop.hbase.regionserver.wal.HLog.getReader(HLog.java:716)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.openReader(ReplicationSource.java:491)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.run(ReplicationSource.java:290)
2012-11-07 15:47:40,927 WARN regionserver.ReplicationSource
(ReplicationSource.java:openReader(547)) - Waited too long for this file,
considering dumping
2012-11-07 15:47:40,927 DEBUG regionserver.ReplicationSource
(ReplicationSource.java:sleepForRetries(562)) - Unable to open a reader,
sleeping 1000 times 10
{code}
We should reduce the log spewing in this case (or some informative message,
based on the offset).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-7122) Proper warning message when opening a log file with no entries (idle cluster)
[
https://issues.apache.org/jira/browse/HBASE-7122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13640335#comment-13640335
]
Hudson commented on HBASE-7122:
---
Integrated in HBase-TRUNK #4077 (See
[https://builds.apache.org/job/HBase-TRUNK/4077/])
HBASE-7122 Proper warning message when opening a log file with no entries
(idle cluster) (Revision 1471255)
Result = FAILURE
stack :
Files :
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/ReplicationSource.java
Proper warning message when opening a log file with no entries (idle cluster)
-
Key: HBASE-7122
URL: https://issues.apache.org/jira/browse/HBASE-7122
Project: HBase
Issue Type: Bug
Components: Replication
Affects Versions: 0.94.2
Reporter: Himanshu Vashishtha
Assignee: Himanshu Vashishtha
Fix For: 0.95.1
Attachments: HBase-7122-94.patch, HBase-7122-95.patch,
HBase-7122-95-v2.patch, HBase-7122-95-v3.patch, HBase-7122-95-v4.patch,
HBase-7122.patch, HBASE-7122.v2.patch
In case the cluster is idle and the log has rolled (offset to 0),
replicationSource tries to open the log and gets an EOF exception. This gets
printed after every 10 sec until an entry is inserted in it.
{code}
2012-11-07 15:47:40,924 DEBUG regionserver.ReplicationSource
(ReplicationSource.java:openReader(487)) - Opening log for replication
c0315.hal.cloudera.com%2C40020%2C1352324202860.1352327804874 at 0
2012-11-07 15:47:40,926 WARN regionserver.ReplicationSource
(ReplicationSource.java:openReader(543)) - 1 Got:
java.io.EOFException
at java.io.DataInputStream.readFully(DataInputStream.java:180)
at java.io.DataInputStream.readFully(DataInputStream.java:152)
at org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1508)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1486)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1475)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1470)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader$WALReader.init(SequenceFileLogReader.java:55)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader.init(SequenceFileLogReader.java:175)
at
org.apache.hadoop.hbase.regionserver.wal.HLog.getReader(HLog.java:716)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.openReader(ReplicationSource.java:491)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.run(ReplicationSource.java:290)
2012-11-07 15:47:40,927 WARN regionserver.ReplicationSource
(ReplicationSource.java:openReader(547)) - Waited too long for this file,
considering dumping
2012-11-07 15:47:40,927 DEBUG regionserver.ReplicationSource
(ReplicationSource.java:sleepForRetries(562)) - Unable to open a reader,
sleeping 1000 times 10
{code}
We should reduce the log spewing in this case (or some informative message,
based on the offset).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-7122) Proper warning message when opening a log file with no entries (idle cluster)
[
https://issues.apache.org/jira/browse/HBASE-7122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13640375#comment-13640375
]
Hudson commented on HBASE-7122:
---
Integrated in hbase-0.95 #160 (See
[https://builds.apache.org/job/hbase-0.95/160/])
HBASE-7122 Proper warning message when opening a log file with no entries
(idle cluster) (Revision 1471256)
Result = FAILURE
stack :
Files :
*
/hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/ReplicationSource.java
Proper warning message when opening a log file with no entries (idle cluster)
-
Key: HBASE-7122
URL: https://issues.apache.org/jira/browse/HBASE-7122
Project: HBase
Issue Type: Bug
Components: Replication
Affects Versions: 0.94.2
Reporter: Himanshu Vashishtha
Assignee: Himanshu Vashishtha
Fix For: 0.95.1
Attachments: HBase-7122-94.patch, HBase-7122-95.patch,
HBase-7122-95-v2.patch, HBase-7122-95-v3.patch, HBase-7122-95-v4.patch,
HBase-7122.patch, HBASE-7122.v2.patch
In case the cluster is idle and the log has rolled (offset to 0),
replicationSource tries to open the log and gets an EOF exception. This gets
printed after every 10 sec until an entry is inserted in it.
{code}
2012-11-07 15:47:40,924 DEBUG regionserver.ReplicationSource
(ReplicationSource.java:openReader(487)) - Opening log for replication
c0315.hal.cloudera.com%2C40020%2C1352324202860.1352327804874 at 0
2012-11-07 15:47:40,926 WARN regionserver.ReplicationSource
(ReplicationSource.java:openReader(543)) - 1 Got:
java.io.EOFException
at java.io.DataInputStream.readFully(DataInputStream.java:180)
at java.io.DataInputStream.readFully(DataInputStream.java:152)
at org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1508)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1486)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1475)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1470)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader$WALReader.init(SequenceFileLogReader.java:55)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader.init(SequenceFileLogReader.java:175)
at
org.apache.hadoop.hbase.regionserver.wal.HLog.getReader(HLog.java:716)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.openReader(ReplicationSource.java:491)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.run(ReplicationSource.java:290)
2012-11-07 15:47:40,927 WARN regionserver.ReplicationSource
(ReplicationSource.java:openReader(547)) - Waited too long for this file,
considering dumping
2012-11-07 15:47:40,927 DEBUG regionserver.ReplicationSource
(ReplicationSource.java:sleepForRetries(562)) - Unable to open a reader,
sleeping 1000 times 10
{code}
We should reduce the log spewing in this case (or some informative message,
based on the offset).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-7122) Proper warning message when opening a log file with no entries (idle cluster)
[
https://issues.apache.org/jira/browse/HBASE-7122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13639599#comment-13639599
]
stack commented on HBASE-7122:
--
Patch looks good. You might change this:
{code}
+if (this.repLogReader.getPosition() == 0 !queueRecovered
queue.size() == 0) return true;
+return false;
{code}
to this
{code}
return this.repLogReader.getPosition() == 0 !queueRecovered
queue.size() == 0;
{code}
When we ask for position in the above, it is not a trip to the NN, right?
Proper warning message when opening a log file with no entries (idle cluster)
-
Key: HBASE-7122
URL: https://issues.apache.org/jira/browse/HBASE-7122
Project: HBase
Issue Type: Bug
Components: Replication
Affects Versions: 0.94.2
Reporter: Himanshu Vashishtha
Assignee: Himanshu Vashishtha
Fix For: 0.95.1
Attachments: HBase-7122-94.patch, HBase-7122-95.patch,
HBase-7122-95-v2.patch, HBase-7122-95-v3.patch, HBase-7122.patch,
HBASE-7122.v2.patch
In case the cluster is idle and the log has rolled (offset to 0),
replicationSource tries to open the log and gets an EOF exception. This gets
printed after every 10 sec until an entry is inserted in it.
{code}
2012-11-07 15:47:40,924 DEBUG regionserver.ReplicationSource
(ReplicationSource.java:openReader(487)) - Opening log for replication
c0315.hal.cloudera.com%2C40020%2C1352324202860.1352327804874 at 0
2012-11-07 15:47:40,926 WARN regionserver.ReplicationSource
(ReplicationSource.java:openReader(543)) - 1 Got:
java.io.EOFException
at java.io.DataInputStream.readFully(DataInputStream.java:180)
at java.io.DataInputStream.readFully(DataInputStream.java:152)
at org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1508)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1486)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1475)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1470)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader$WALReader.init(SequenceFileLogReader.java:55)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader.init(SequenceFileLogReader.java:175)
at
org.apache.hadoop.hbase.regionserver.wal.HLog.getReader(HLog.java:716)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.openReader(ReplicationSource.java:491)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.run(ReplicationSource.java:290)
2012-11-07 15:47:40,927 WARN regionserver.ReplicationSource
(ReplicationSource.java:openReader(547)) - Waited too long for this file,
considering dumping
2012-11-07 15:47:40,927 DEBUG regionserver.ReplicationSource
(ReplicationSource.java:sleepForRetries(562)) - Unable to open a reader,
sleeping 1000 times 10
{code}
We should reduce the log spewing in this case (or some informative message,
based on the offset).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-7122) Proper warning message when opening a log file with no entries (idle cluster)
[
https://issues.apache.org/jira/browse/HBASE-7122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13639623#comment-13639623
]
Chris Trezzo commented on HBASE-7122:
-
[~saint@gmail.com] getPosition is not a round trip and is just the position
that the ReplicationHLogReaderManager keeps locally.
Looked over the patch again, and it looks good to me. Even though I missed the
first problem (Nice catch [~jeason])!
Proper warning message when opening a log file with no entries (idle cluster)
-
Key: HBASE-7122
URL: https://issues.apache.org/jira/browse/HBASE-7122
Project: HBase
Issue Type: Bug
Components: Replication
Affects Versions: 0.94.2
Reporter: Himanshu Vashishtha
Assignee: Himanshu Vashishtha
Fix For: 0.95.1
Attachments: HBase-7122-94.patch, HBase-7122-95.patch,
HBase-7122-95-v2.patch, HBase-7122-95-v3.patch, HBase-7122.patch,
HBASE-7122.v2.patch
In case the cluster is idle and the log has rolled (offset to 0),
replicationSource tries to open the log and gets an EOF exception. This gets
printed after every 10 sec until an entry is inserted in it.
{code}
2012-11-07 15:47:40,924 DEBUG regionserver.ReplicationSource
(ReplicationSource.java:openReader(487)) - Opening log for replication
c0315.hal.cloudera.com%2C40020%2C1352324202860.1352327804874 at 0
2012-11-07 15:47:40,926 WARN regionserver.ReplicationSource
(ReplicationSource.java:openReader(543)) - 1 Got:
java.io.EOFException
at java.io.DataInputStream.readFully(DataInputStream.java:180)
at java.io.DataInputStream.readFully(DataInputStream.java:152)
at org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1508)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1486)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1475)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1470)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader$WALReader.init(SequenceFileLogReader.java:55)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader.init(SequenceFileLogReader.java:175)
at
org.apache.hadoop.hbase.regionserver.wal.HLog.getReader(HLog.java:716)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.openReader(ReplicationSource.java:491)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.run(ReplicationSource.java:290)
2012-11-07 15:47:40,927 WARN regionserver.ReplicationSource
(ReplicationSource.java:openReader(547)) - Waited too long for this file,
considering dumping
2012-11-07 15:47:40,927 DEBUG regionserver.ReplicationSource
(ReplicationSource.java:sleepForRetries(562)) - Unable to open a reader,
sleeping 1000 times 10
{code}
We should reduce the log spewing in this case (or some informative message,
based on the offset).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-7122) Proper warning message when opening a log file with no entries (idle cluster)
[
https://issues.apache.org/jira/browse/HBASE-7122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13639712#comment-13639712
]
Hadoop QA commented on HBASE-7122:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12580133/HBase-7122-95-v4.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 hadoop1.0{color}. The patch compiles against the hadoop
1.0 profile.
{color:green}+1 hadoop2.0{color}. The patch compiles against the hadoop
2.0 profile.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/5412//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5412//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5412//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5412//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5412//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5412//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5412//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5412//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5412//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/5412//console
This message is automatically generated.
Proper warning message when opening a log file with no entries (idle cluster)
-
Key: HBASE-7122
URL: https://issues.apache.org/jira/browse/HBASE-7122
Project: HBase
Issue Type: Bug
Components: Replication
Affects Versions: 0.94.2
Reporter: Himanshu Vashishtha
Assignee: Himanshu Vashishtha
Fix For: 0.95.1
Attachments: HBase-7122-94.patch, HBase-7122-95.patch,
HBase-7122-95-v2.patch, HBase-7122-95-v3.patch, HBase-7122-95-v4.patch,
HBase-7122.patch, HBASE-7122.v2.patch
In case the cluster is idle and the log has rolled (offset to 0),
replicationSource tries to open the log and gets an EOF exception. This gets
printed after every 10 sec until an entry is inserted in it.
{code}
2012-11-07 15:47:40,924 DEBUG regionserver.ReplicationSource
(ReplicationSource.java:openReader(487)) - Opening log for replication
c0315.hal.cloudera.com%2C40020%2C1352324202860.1352327804874 at 0
2012-11-07 15:47:40,926 WARN regionserver.ReplicationSource
(ReplicationSource.java:openReader(543)) - 1 Got:
java.io.EOFException
at java.io.DataInputStream.readFully(DataInputStream.java:180)
at java.io.DataInputStream.readFully(DataInputStream.java:152)
at org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1508)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1486)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1475)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1470)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader$WALReader.init(SequenceFileLogReader.java:55)
at
[jira] [Commented] (HBASE-7122) Proper warning message when opening a log file with no entries (idle cluster)
[
https://issues.apache.org/jira/browse/HBASE-7122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13628764#comment-13628764
]
Hadoop QA commented on HBASE-7122:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12578161/HBase-7122-95-v3.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 hadoop2.0{color}. The patch compiles against the hadoop
2.0 profile.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/5260//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5260//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5260//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5260//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5260//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5260//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5260//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5260//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5260//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/5260//console
This message is automatically generated.
Proper warning message when opening a log file with no entries (idle cluster)
-
Key: HBASE-7122
URL: https://issues.apache.org/jira/browse/HBASE-7122
Project: HBase
Issue Type: Bug
Components: Replication
Affects Versions: 0.94.2
Reporter: Himanshu Vashishtha
Assignee: Himanshu Vashishtha
Fix For: 0.95.1
Attachments: HBase-7122-94.patch, HBase-7122-95.patch,
HBase-7122-95-v2.patch, HBase-7122-95-v3.patch, HBase-7122.patch,
HBASE-7122.v2.patch
In case the cluster is idle and the log has rolled (offset to 0),
replicationSource tries to open the log and gets an EOF exception. This gets
printed after every 10 sec until an entry is inserted in it.
{code}
2012-11-07 15:47:40,924 DEBUG regionserver.ReplicationSource
(ReplicationSource.java:openReader(487)) - Opening log for replication
c0315.hal.cloudera.com%2C40020%2C1352324202860.1352327804874 at 0
2012-11-07 15:47:40,926 WARN regionserver.ReplicationSource
(ReplicationSource.java:openReader(543)) - 1 Got:
java.io.EOFException
at java.io.DataInputStream.readFully(DataInputStream.java:180)
at java.io.DataInputStream.readFully(DataInputStream.java:152)
at org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1508)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1486)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1475)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1470)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader$WALReader.init(SequenceFileLogReader.java:55)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader.init(SequenceFileLogReader.java:175)
at
[jira] [Commented] (HBASE-7122) Proper warning message when opening a log file with no entries (idle cluster)
[
https://issues.apache.org/jira/browse/HBASE-7122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13626323#comment-13626323
]
Jieshan Bean commented on HBASE-7122:
-
Yes, HLog is not empty if it closed succesfully. We may not get EOF.
But if we get IOE during close, what will happen?
Proper warning message when opening a log file with no entries (idle cluster)
-
Key: HBASE-7122
URL: https://issues.apache.org/jira/browse/HBASE-7122
Project: HBase
Issue Type: Bug
Components: Replication
Affects Versions: 0.94.2
Reporter: Himanshu Vashishtha
Assignee: Himanshu Vashishtha
Fix For: 0.95.1
Attachments: HBase-7122-94.patch, HBase-7122-95.patch,
HBase-7122.patch, HBASE-7122.v2.patch
In case the cluster is idle and the log has rolled (offset to 0),
replicationSource tries to open the log and gets an EOF exception. This gets
printed after every 10 sec until an entry is inserted in it.
{code}
2012-11-07 15:47:40,924 DEBUG regionserver.ReplicationSource
(ReplicationSource.java:openReader(487)) - Opening log for replication
c0315.hal.cloudera.com%2C40020%2C1352324202860.1352327804874 at 0
2012-11-07 15:47:40,926 WARN regionserver.ReplicationSource
(ReplicationSource.java:openReader(543)) - 1 Got:
java.io.EOFException
at java.io.DataInputStream.readFully(DataInputStream.java:180)
at java.io.DataInputStream.readFully(DataInputStream.java:152)
at org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1508)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1486)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1475)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1470)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader$WALReader.init(SequenceFileLogReader.java:55)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader.init(SequenceFileLogReader.java:175)
at
org.apache.hadoop.hbase.regionserver.wal.HLog.getReader(HLog.java:716)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.openReader(ReplicationSource.java:491)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.run(ReplicationSource.java:290)
2012-11-07 15:47:40,927 WARN regionserver.ReplicationSource
(ReplicationSource.java:openReader(547)) - Waited too long for this file,
considering dumping
2012-11-07 15:47:40,927 DEBUG regionserver.ReplicationSource
(ReplicationSource.java:sleepForRetries(562)) - Unable to open a reader,
sleeping 1000 times 10
{code}
We should reduce the log spewing in this case (or some informative message,
based on the offset).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-7122) Proper warning message when opening a log file with no entries (idle cluster)
[
https://issues.apache.org/jira/browse/HBASE-7122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13626967#comment-13626967
]
Hadoop QA commented on HBASE-7122:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12577844/HBase-7122-95-v2.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 hadoop2.0{color}. The patch compiles against the hadoop
2.0 profile.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/5224//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5224//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5224//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5224//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5224//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5224//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5224//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5224//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5224//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/5224//console
This message is automatically generated.
Proper warning message when opening a log file with no entries (idle cluster)
-
Key: HBASE-7122
URL: https://issues.apache.org/jira/browse/HBASE-7122
Project: HBase
Issue Type: Bug
Components: Replication
Affects Versions: 0.94.2
Reporter: Himanshu Vashishtha
Assignee: Himanshu Vashishtha
Fix For: 0.95.1
Attachments: HBase-7122-94.patch, HBase-7122-95.patch,
HBase-7122-95-v2.patch, HBase-7122.patch, HBASE-7122.v2.patch
In case the cluster is idle and the log has rolled (offset to 0),
replicationSource tries to open the log and gets an EOF exception. This gets
printed after every 10 sec until an entry is inserted in it.
{code}
2012-11-07 15:47:40,924 DEBUG regionserver.ReplicationSource
(ReplicationSource.java:openReader(487)) - Opening log for replication
c0315.hal.cloudera.com%2C40020%2C1352324202860.1352327804874 at 0
2012-11-07 15:47:40,926 WARN regionserver.ReplicationSource
(ReplicationSource.java:openReader(543)) - 1 Got:
java.io.EOFException
at java.io.DataInputStream.readFully(DataInputStream.java:180)
at java.io.DataInputStream.readFully(DataInputStream.java:152)
at org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1508)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1486)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1475)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1470)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader$WALReader.init(SequenceFileLogReader.java:55)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader.init(SequenceFileLogReader.java:175)
at
[jira] [Commented] (HBASE-7122) Proper warning message when opening a log file with no entries (idle cluster)
[
https://issues.apache.org/jira/browse/HBASE-7122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13627326#comment-13627326
]
Jieshan Bean commented on HBASE-7122:
-
+1 on patch v2.
Proper warning message when opening a log file with no entries (idle cluster)
-
Key: HBASE-7122
URL: https://issues.apache.org/jira/browse/HBASE-7122
Project: HBase
Issue Type: Bug
Components: Replication
Affects Versions: 0.94.2
Reporter: Himanshu Vashishtha
Assignee: Himanshu Vashishtha
Fix For: 0.95.1
Attachments: HBase-7122-94.patch, HBase-7122-95.patch,
HBase-7122-95-v2.patch, HBase-7122.patch, HBASE-7122.v2.patch
In case the cluster is idle and the log has rolled (offset to 0),
replicationSource tries to open the log and gets an EOF exception. This gets
printed after every 10 sec until an entry is inserted in it.
{code}
2012-11-07 15:47:40,924 DEBUG regionserver.ReplicationSource
(ReplicationSource.java:openReader(487)) - Opening log for replication
c0315.hal.cloudera.com%2C40020%2C1352324202860.1352327804874 at 0
2012-11-07 15:47:40,926 WARN regionserver.ReplicationSource
(ReplicationSource.java:openReader(543)) - 1 Got:
java.io.EOFException
at java.io.DataInputStream.readFully(DataInputStream.java:180)
at java.io.DataInputStream.readFully(DataInputStream.java:152)
at org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1508)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1486)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1475)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1470)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader$WALReader.init(SequenceFileLogReader.java:55)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader.init(SequenceFileLogReader.java:175)
at
org.apache.hadoop.hbase.regionserver.wal.HLog.getReader(HLog.java:716)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.openReader(ReplicationSource.java:491)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.run(ReplicationSource.java:290)
2012-11-07 15:47:40,927 WARN regionserver.ReplicationSource
(ReplicationSource.java:openReader(547)) - Waited too long for this file,
considering dumping
2012-11-07 15:47:40,927 DEBUG regionserver.ReplicationSource
(ReplicationSource.java:sleepForRetries(562)) - Unable to open a reader,
sleeping 1000 times 10
{code}
We should reduce the log spewing in this case (or some informative message,
based on the offset).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-7122) Proper warning message when opening a log file with no entries (idle cluster)
[
https://issues.apache.org/jira/browse/HBASE-7122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13627359#comment-13627359
]
Jieshan Bean commented on HBASE-7122:
-
BTW, one minor comment:). Please add curly brackets to the below code:
{code}
+if (this.repLogReader.getPosition() == 0 !queueRecovered
queue.size() == 0)
+ return true;
{code}
Proper warning message when opening a log file with no entries (idle cluster)
-
Key: HBASE-7122
URL: https://issues.apache.org/jira/browse/HBASE-7122
Project: HBase
Issue Type: Bug
Components: Replication
Affects Versions: 0.94.2
Reporter: Himanshu Vashishtha
Assignee: Himanshu Vashishtha
Fix For: 0.95.1
Attachments: HBase-7122-94.patch, HBase-7122-95.patch,
HBase-7122-95-v2.patch, HBase-7122.patch, HBASE-7122.v2.patch
In case the cluster is idle and the log has rolled (offset to 0),
replicationSource tries to open the log and gets an EOF exception. This gets
printed after every 10 sec until an entry is inserted in it.
{code}
2012-11-07 15:47:40,924 DEBUG regionserver.ReplicationSource
(ReplicationSource.java:openReader(487)) - Opening log for replication
c0315.hal.cloudera.com%2C40020%2C1352324202860.1352327804874 at 0
2012-11-07 15:47:40,926 WARN regionserver.ReplicationSource
(ReplicationSource.java:openReader(543)) - 1 Got:
java.io.EOFException
at java.io.DataInputStream.readFully(DataInputStream.java:180)
at java.io.DataInputStream.readFully(DataInputStream.java:152)
at org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1508)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1486)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1475)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1470)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader$WALReader.init(SequenceFileLogReader.java:55)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader.init(SequenceFileLogReader.java:175)
at
org.apache.hadoop.hbase.regionserver.wal.HLog.getReader(HLog.java:716)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.openReader(ReplicationSource.java:491)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.run(ReplicationSource.java:290)
2012-11-07 15:47:40,927 WARN regionserver.ReplicationSource
(ReplicationSource.java:openReader(547)) - Waited too long for this file,
considering dumping
2012-11-07 15:47:40,927 DEBUG regionserver.ReplicationSource
(ReplicationSource.java:sleepForRetries(562)) - Unable to open a reader,
sleeping 1000 times 10
{code}
We should reduce the log spewing in this case (or some informative message,
based on the offset).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-7122) Proper warning message when opening a log file with no entries (idle cluster)
[
https://issues.apache.org/jira/browse/HBASE-7122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13625878#comment-13625878
]
Himanshu Vashishtha commented on HBASE-7122:
Yes, will upload a new patch.
Proper warning message when opening a log file with no entries (idle cluster)
-
Key: HBASE-7122
URL: https://issues.apache.org/jira/browse/HBASE-7122
Project: HBase
Issue Type: Bug
Components: Replication
Affects Versions: 0.94.2
Reporter: Himanshu Vashishtha
Assignee: Himanshu Vashishtha
Fix For: 0.95.1
Attachments: HBase-7122-94.patch, HBase-7122.patch,
HBASE-7122.v2.patch
In case the cluster is idle and the log has rolled (offset to 0),
replicationSource tries to open the log and gets an EOF exception. This gets
printed after every 10 sec until an entry is inserted in it.
{code}
2012-11-07 15:47:40,924 DEBUG regionserver.ReplicationSource
(ReplicationSource.java:openReader(487)) - Opening log for replication
c0315.hal.cloudera.com%2C40020%2C1352324202860.1352327804874 at 0
2012-11-07 15:47:40,926 WARN regionserver.ReplicationSource
(ReplicationSource.java:openReader(543)) - 1 Got:
java.io.EOFException
at java.io.DataInputStream.readFully(DataInputStream.java:180)
at java.io.DataInputStream.readFully(DataInputStream.java:152)
at org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1508)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1486)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1475)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1470)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader$WALReader.init(SequenceFileLogReader.java:55)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader.init(SequenceFileLogReader.java:175)
at
org.apache.hadoop.hbase.regionserver.wal.HLog.getReader(HLog.java:716)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.openReader(ReplicationSource.java:491)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.run(ReplicationSource.java:290)
2012-11-07 15:47:40,927 WARN regionserver.ReplicationSource
(ReplicationSource.java:openReader(547)) - Waited too long for this file,
considering dumping
2012-11-07 15:47:40,927 DEBUG regionserver.ReplicationSource
(ReplicationSource.java:sleepForRetries(562)) - Unable to open a reader,
sleeping 1000 times 10
{code}
We should reduce the log spewing in this case (or some informative message,
based on the offset).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-7122) Proper warning message when opening a log file with no entries (idle cluster)
[
https://issues.apache.org/jira/browse/HBASE-7122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13626043#comment-13626043
]
Jieshan Bean commented on HBASE-7122:
-
I think add this check is not enough. There still has the chance of empty
log(Not the writing one) in normal log list.
So we need to check whether this log is the one in use.
Proper warning message when opening a log file with no entries (idle cluster)
-
Key: HBASE-7122
URL: https://issues.apache.org/jira/browse/HBASE-7122
Project: HBase
Issue Type: Bug
Components: Replication
Affects Versions: 0.94.2
Reporter: Himanshu Vashishtha
Assignee: Himanshu Vashishtha
Fix For: 0.95.1
Attachments: HBase-7122-94.patch, HBase-7122-95.patch,
HBase-7122.patch, HBASE-7122.v2.patch
In case the cluster is idle and the log has rolled (offset to 0),
replicationSource tries to open the log and gets an EOF exception. This gets
printed after every 10 sec until an entry is inserted in it.
{code}
2012-11-07 15:47:40,924 DEBUG regionserver.ReplicationSource
(ReplicationSource.java:openReader(487)) - Opening log for replication
c0315.hal.cloudera.com%2C40020%2C1352324202860.1352327804874 at 0
2012-11-07 15:47:40,926 WARN regionserver.ReplicationSource
(ReplicationSource.java:openReader(543)) - 1 Got:
java.io.EOFException
at java.io.DataInputStream.readFully(DataInputStream.java:180)
at java.io.DataInputStream.readFully(DataInputStream.java:152)
at org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1508)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1486)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1475)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1470)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader$WALReader.init(SequenceFileLogReader.java:55)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader.init(SequenceFileLogReader.java:175)
at
org.apache.hadoop.hbase.regionserver.wal.HLog.getReader(HLog.java:716)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.openReader(ReplicationSource.java:491)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.run(ReplicationSource.java:290)
2012-11-07 15:47:40,927 WARN regionserver.ReplicationSource
(ReplicationSource.java:openReader(547)) - Waited too long for this file,
considering dumping
2012-11-07 15:47:40,927 DEBUG regionserver.ReplicationSource
(ReplicationSource.java:sleepForRetries(562)) - Unable to open a reader,
sleeping 1000 times 10
{code}
We should reduce the log spewing in this case (or some informative message,
based on the offset).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-7122) Proper warning message when opening a log file with no entries (idle cluster)
[
https://issues.apache.org/jira/browse/HBASE-7122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13626240#comment-13626240
]
Himanshu Vashishtha commented on HBASE-7122:
I thought it over too.
bq. There still has the chance of empty log(Not the writing one) in normal log
list.
When do you see this happening? If there are no entries in a log, we usually
don't roll. Even if we do roll, we insert some meta data which make its size
134 bytes.
On an ideal cluster:
{code}
hbase(main):009:0 hlog_roll 'localhost,60020,1365483729051'
0 row(s) in 0.0210 seconds
hbase(main):010:0 hlog_roll 'localhost,60020,1365483729051'
0 row(s) in 0.0170 seconds
hbase(main):011:0 hlog_roll 'localhost,60020,1365483729051'
0 row(s) in 0.0160 seconds
{code}
I see log files of size 134 bytes in the log directory.
{code}
-rwxrwxrwx 1 himanshu himanshu 1008 2013-04-08 23:08
localhost%2C60020%2C1365483729051.1365483729440
-rwxrwxrwx 1 himanshu himanshu 134 2013-04-08 23:08
localhost%2C60020%2C1365483729051.1365484108125
-rwxrwxrwx 1 himanshu himanshu 134 2013-04-08 23:09
localhost%2C60020%2C1365483729051.1365484126213
-rwxrwxrwx 1 himanshu himanshu0 2013-04-08 23:09
localhost%2C60020%2C1365483729051.1365484193328
{code}
The middle two ones are the ones which didn't see any mutations as such.
Proper warning message when opening a log file with no entries (idle cluster)
-
Key: HBASE-7122
URL: https://issues.apache.org/jira/browse/HBASE-7122
Project: HBase
Issue Type: Bug
Components: Replication
Affects Versions: 0.94.2
Reporter: Himanshu Vashishtha
Assignee: Himanshu Vashishtha
Fix For: 0.95.1
Attachments: HBase-7122-94.patch, HBase-7122-95.patch,
HBase-7122.patch, HBASE-7122.v2.patch
In case the cluster is idle and the log has rolled (offset to 0),
replicationSource tries to open the log and gets an EOF exception. This gets
printed after every 10 sec until an entry is inserted in it.
{code}
2012-11-07 15:47:40,924 DEBUG regionserver.ReplicationSource
(ReplicationSource.java:openReader(487)) - Opening log for replication
c0315.hal.cloudera.com%2C40020%2C1352324202860.1352327804874 at 0
2012-11-07 15:47:40,926 WARN regionserver.ReplicationSource
(ReplicationSource.java:openReader(543)) - 1 Got:
java.io.EOFException
at java.io.DataInputStream.readFully(DataInputStream.java:180)
at java.io.DataInputStream.readFully(DataInputStream.java:152)
at org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1508)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1486)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1475)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1470)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader$WALReader.init(SequenceFileLogReader.java:55)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader.init(SequenceFileLogReader.java:175)
at
org.apache.hadoop.hbase.regionserver.wal.HLog.getReader(HLog.java:716)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.openReader(ReplicationSource.java:491)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.run(ReplicationSource.java:290)
2012-11-07 15:47:40,927 WARN regionserver.ReplicationSource
(ReplicationSource.java:openReader(547)) - Waited too long for this file,
considering dumping
2012-11-07 15:47:40,927 DEBUG regionserver.ReplicationSource
(ReplicationSource.java:sleepForRetries(562)) - Unable to open a reader,
sleeping 1000 times 10
{code}
We should reduce the log spewing in this case (or some informative message,
based on the offset).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-7122) Proper warning message when opening a log file with no entries (idle cluster)
[
https://issues.apache.org/jira/browse/HBASE-7122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13621531#comment-13621531
]
stack commented on HBASE-7122:
--
[~himan...@cloudera.com] What you think of [~jeason] comment above?
Proper warning message when opening a log file with no entries (idle cluster)
-
Key: HBASE-7122
URL: https://issues.apache.org/jira/browse/HBASE-7122
Project: HBase
Issue Type: Bug
Components: Replication
Affects Versions: 0.94.2
Reporter: Himanshu Vashishtha
Assignee: Himanshu Vashishtha
Fix For: 0.95.0
Attachments: HBase-7122-94.patch, HBase-7122.patch,
HBASE-7122.v2.patch
In case the cluster is idle and the log has rolled (offset to 0),
replicationSource tries to open the log and gets an EOF exception. This gets
printed after every 10 sec until an entry is inserted in it.
{code}
2012-11-07 15:47:40,924 DEBUG regionserver.ReplicationSource
(ReplicationSource.java:openReader(487)) - Opening log for replication
c0315.hal.cloudera.com%2C40020%2C1352324202860.1352327804874 at 0
2012-11-07 15:47:40,926 WARN regionserver.ReplicationSource
(ReplicationSource.java:openReader(543)) - 1 Got:
java.io.EOFException
at java.io.DataInputStream.readFully(DataInputStream.java:180)
at java.io.DataInputStream.readFully(DataInputStream.java:152)
at org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1508)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1486)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1475)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1470)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader$WALReader.init(SequenceFileLogReader.java:55)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader.init(SequenceFileLogReader.java:175)
at
org.apache.hadoop.hbase.regionserver.wal.HLog.getReader(HLog.java:716)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.openReader(ReplicationSource.java:491)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.run(ReplicationSource.java:290)
2012-11-07 15:47:40,927 WARN regionserver.ReplicationSource
(ReplicationSource.java:openReader(547)) - Waited too long for this file,
considering dumping
2012-11-07 15:47:40,927 DEBUG regionserver.ReplicationSource
(ReplicationSource.java:sleepForRetries(562)) - Unable to open a reader,
sleeping 1000 times 10
{code}
We should reduce the log spewing in this case (or some informative message,
based on the offset).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-7122) Proper warning message when opening a log file with no entries (idle cluster)
[
https://issues.apache.org/jira/browse/HBASE-7122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13616115#comment-13616115
]
Jieshan Bean commented on HBASE-7122:
-
[~himan...@cloudera.com] There's one possible problem in this patch. Suppose we
have several logs in recovered queue and with 1 log is empty, this change will
hang the ReplicationSource thread which will keep opening the empty log.
Proper warning message when opening a log file with no entries (idle cluster)
-
Key: HBASE-7122
URL: https://issues.apache.org/jira/browse/HBASE-7122
Project: HBase
Issue Type: Bug
Components: Replication
Affects Versions: 0.94.2
Reporter: Himanshu Vashishtha
Assignee: Himanshu Vashishtha
Fix For: 0.95.0
Attachments: HBase-7122-94.patch, HBase-7122.patch,
HBASE-7122.v2.patch
In case the cluster is idle and the log has rolled (offset to 0),
replicationSource tries to open the log and gets an EOF exception. This gets
printed after every 10 sec until an entry is inserted in it.
{code}
2012-11-07 15:47:40,924 DEBUG regionserver.ReplicationSource
(ReplicationSource.java:openReader(487)) - Opening log for replication
c0315.hal.cloudera.com%2C40020%2C1352324202860.1352327804874 at 0
2012-11-07 15:47:40,926 WARN regionserver.ReplicationSource
(ReplicationSource.java:openReader(543)) - 1 Got:
java.io.EOFException
at java.io.DataInputStream.readFully(DataInputStream.java:180)
at java.io.DataInputStream.readFully(DataInputStream.java:152)
at org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1508)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1486)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1475)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1470)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader$WALReader.init(SequenceFileLogReader.java:55)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader.init(SequenceFileLogReader.java:175)
at
org.apache.hadoop.hbase.regionserver.wal.HLog.getReader(HLog.java:716)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.openReader(ReplicationSource.java:491)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.run(ReplicationSource.java:290)
2012-11-07 15:47:40,927 WARN regionserver.ReplicationSource
(ReplicationSource.java:openReader(547)) - Waited too long for this file,
considering dumping
2012-11-07 15:47:40,927 DEBUG regionserver.ReplicationSource
(ReplicationSource.java:sleepForRetries(562)) - Unable to open a reader,
sleeping 1000 times 10
{code}
We should reduce the log spewing in this case (or some informative message,
based on the offset).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-7122) Proper warning message when opening a log file with no entries (idle cluster)
[
https://issues.apache.org/jira/browse/HBASE-7122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13606983#comment-13606983
]
Chris Trezzo commented on HBASE-7122:
-
Patch looks good to me as well.
Proper warning message when opening a log file with no entries (idle cluster)
-
Key: HBASE-7122
URL: https://issues.apache.org/jira/browse/HBASE-7122
Project: HBase
Issue Type: Bug
Components: Replication
Affects Versions: 0.94.2
Reporter: Himanshu Vashishtha
Assignee: Himanshu Vashishtha
Fix For: 0.95.0
Attachments: HBase-7122-94.patch, HBase-7122.patch,
HBASE-7122.v2.patch
In case the cluster is idle and the log has rolled (offset to 0),
replicationSource tries to open the log and gets an EOF exception. This gets
printed after every 10 sec until an entry is inserted in it.
{code}
2012-11-07 15:47:40,924 DEBUG regionserver.ReplicationSource
(ReplicationSource.java:openReader(487)) - Opening log for replication
c0315.hal.cloudera.com%2C40020%2C1352324202860.1352327804874 at 0
2012-11-07 15:47:40,926 WARN regionserver.ReplicationSource
(ReplicationSource.java:openReader(543)) - 1 Got:
java.io.EOFException
at java.io.DataInputStream.readFully(DataInputStream.java:180)
at java.io.DataInputStream.readFully(DataInputStream.java:152)
at org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1508)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1486)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1475)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1470)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader$WALReader.init(SequenceFileLogReader.java:55)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader.init(SequenceFileLogReader.java:175)
at
org.apache.hadoop.hbase.regionserver.wal.HLog.getReader(HLog.java:716)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.openReader(ReplicationSource.java:491)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.run(ReplicationSource.java:290)
2012-11-07 15:47:40,927 WARN regionserver.ReplicationSource
(ReplicationSource.java:openReader(547)) - Waited too long for this file,
considering dumping
2012-11-07 15:47:40,927 DEBUG regionserver.ReplicationSource
(ReplicationSource.java:sleepForRetries(562)) - Unable to open a reader,
sleeping 1000 times 10
{code}
We should reduce the log spewing in this case (or some informative message,
based on the offset).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-7122) Proper warning message when opening a log file with no entries (idle cluster)
[
https://issues.apache.org/jira/browse/HBASE-7122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13602888#comment-13602888
]
Lars Hofhansl commented on HBASE-7122:
--
+1 on all branches.
Proper warning message when opening a log file with no entries (idle cluster)
-
Key: HBASE-7122
URL: https://issues.apache.org/jira/browse/HBASE-7122
Project: HBase
Issue Type: Bug
Components: Replication
Affects Versions: 0.94.2
Reporter: Himanshu Vashishtha
Assignee: Himanshu Vashishtha
Fix For: 0.95.0
Attachments: HBase-7122-94.patch, HBase-7122.patch,
HBASE-7122.v2.patch
In case the cluster is idle and the log has rolled (offset to 0),
replicationSource tries to open the log and gets an EOF exception. This gets
printed after every 10 sec until an entry is inserted in it.
{code}
2012-11-07 15:47:40,924 DEBUG regionserver.ReplicationSource
(ReplicationSource.java:openReader(487)) - Opening log for replication
c0315.hal.cloudera.com%2C40020%2C1352324202860.1352327804874 at 0
2012-11-07 15:47:40,926 WARN regionserver.ReplicationSource
(ReplicationSource.java:openReader(543)) - 1 Got:
java.io.EOFException
at java.io.DataInputStream.readFully(DataInputStream.java:180)
at java.io.DataInputStream.readFully(DataInputStream.java:152)
at org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1508)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1486)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1475)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1470)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader$WALReader.init(SequenceFileLogReader.java:55)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader.init(SequenceFileLogReader.java:175)
at
org.apache.hadoop.hbase.regionserver.wal.HLog.getReader(HLog.java:716)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.openReader(ReplicationSource.java:491)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.run(ReplicationSource.java:290)
2012-11-07 15:47:40,927 WARN regionserver.ReplicationSource
(ReplicationSource.java:openReader(547)) - Waited too long for this file,
considering dumping
2012-11-07 15:47:40,927 DEBUG regionserver.ReplicationSource
(ReplicationSource.java:sleepForRetries(562)) - Unable to open a reader,
sleeping 1000 times 10
{code}
We should reduce the log spewing in this case (or some informative message,
based on the offset).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-7122) Proper warning message when opening a log file with no entries (idle cluster)
[
https://issues.apache.org/jira/browse/HBASE-7122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13601967#comment-13601967
]
Himanshu Vashishtha commented on HBASE-7122:
will upload a revised patch for 0.94 soon.
Proper warning message when opening a log file with no entries (idle cluster)
-
Key: HBASE-7122
URL: https://issues.apache.org/jira/browse/HBASE-7122
Project: HBase
Issue Type: Sub-task
Components: Replication
Affects Versions: 0.94.2
Reporter: Himanshu Vashishtha
Assignee: Himanshu Vashishtha
Fix For: 0.95.0
Attachments: HBase-7122.patch, HBASE-7122.v2.patch
In case the cluster is idle and the log has rolled (offset to 0),
replicationSource tries to open the log and gets an EOF exception. This gets
printed after every 10 sec until an entry is inserted in it.
{code}
2012-11-07 15:47:40,924 DEBUG regionserver.ReplicationSource
(ReplicationSource.java:openReader(487)) - Opening log for replication
c0315.hal.cloudera.com%2C40020%2C1352324202860.1352327804874 at 0
2012-11-07 15:47:40,926 WARN regionserver.ReplicationSource
(ReplicationSource.java:openReader(543)) - 1 Got:
java.io.EOFException
at java.io.DataInputStream.readFully(DataInputStream.java:180)
at java.io.DataInputStream.readFully(DataInputStream.java:152)
at org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1508)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1486)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1475)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1470)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader$WALReader.init(SequenceFileLogReader.java:55)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader.init(SequenceFileLogReader.java:175)
at
org.apache.hadoop.hbase.regionserver.wal.HLog.getReader(HLog.java:716)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.openReader(ReplicationSource.java:491)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.run(ReplicationSource.java:290)
2012-11-07 15:47:40,927 WARN regionserver.ReplicationSource
(ReplicationSource.java:openReader(547)) - Waited too long for this file,
considering dumping
2012-11-07 15:47:40,927 DEBUG regionserver.ReplicationSource
(ReplicationSource.java:sleepForRetries(562)) - Unable to open a reader,
sleeping 1000 times 10
{code}
We should reduce the log spewing in this case (or some informative message,
based on the offset).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-7122) Proper warning message when opening a log file with no entries (idle cluster)
[
https://issues.apache.org/jira/browse/HBASE-7122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13601980#comment-13601980
]
Hadoop QA commented on HBASE-7122:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12573657/HBase-7122-94.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/4809//console
This message is automatically generated.
Proper warning message when opening a log file with no entries (idle cluster)
-
Key: HBASE-7122
URL: https://issues.apache.org/jira/browse/HBASE-7122
Project: HBase
Issue Type: Bug
Components: Replication
Affects Versions: 0.94.2
Reporter: Himanshu Vashishtha
Assignee: Himanshu Vashishtha
Fix For: 0.95.0
Attachments: HBase-7122-94.patch, HBase-7122.patch,
HBASE-7122.v2.patch
In case the cluster is idle and the log has rolled (offset to 0),
replicationSource tries to open the log and gets an EOF exception. This gets
printed after every 10 sec until an entry is inserted in it.
{code}
2012-11-07 15:47:40,924 DEBUG regionserver.ReplicationSource
(ReplicationSource.java:openReader(487)) - Opening log for replication
c0315.hal.cloudera.com%2C40020%2C1352324202860.1352327804874 at 0
2012-11-07 15:47:40,926 WARN regionserver.ReplicationSource
(ReplicationSource.java:openReader(543)) - 1 Got:
java.io.EOFException
at java.io.DataInputStream.readFully(DataInputStream.java:180)
at java.io.DataInputStream.readFully(DataInputStream.java:152)
at org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1508)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1486)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1475)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1470)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader$WALReader.init(SequenceFileLogReader.java:55)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader.init(SequenceFileLogReader.java:175)
at
org.apache.hadoop.hbase.regionserver.wal.HLog.getReader(HLog.java:716)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.openReader(ReplicationSource.java:491)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.run(ReplicationSource.java:290)
2012-11-07 15:47:40,927 WARN regionserver.ReplicationSource
(ReplicationSource.java:openReader(547)) - Waited too long for this file,
considering dumping
2012-11-07 15:47:40,927 DEBUG regionserver.ReplicationSource
(ReplicationSource.java:sleepForRetries(562)) - Unable to open a reader,
sleeping 1000 times 10
{code}
We should reduce the log spewing in this case (or some informative message,
based on the offset).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-7122) Proper warning message when opening a log file with no entries (idle cluster)
[
https://issues.apache.org/jira/browse/HBASE-7122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13601985#comment-13601985
]
Himanshu Vashishtha commented on HBASE-7122:
trunk patch is still good to apply.
Proper warning message when opening a log file with no entries (idle cluster)
-
Key: HBASE-7122
URL: https://issues.apache.org/jira/browse/HBASE-7122
Project: HBase
Issue Type: Bug
Components: Replication
Affects Versions: 0.94.2
Reporter: Himanshu Vashishtha
Assignee: Himanshu Vashishtha
Fix For: 0.95.0
Attachments: HBase-7122-94.patch, HBase-7122.patch,
HBASE-7122.v2.patch
In case the cluster is idle and the log has rolled (offset to 0),
replicationSource tries to open the log and gets an EOF exception. This gets
printed after every 10 sec until an entry is inserted in it.
{code}
2012-11-07 15:47:40,924 DEBUG regionserver.ReplicationSource
(ReplicationSource.java:openReader(487)) - Opening log for replication
c0315.hal.cloudera.com%2C40020%2C1352324202860.1352327804874 at 0
2012-11-07 15:47:40,926 WARN regionserver.ReplicationSource
(ReplicationSource.java:openReader(543)) - 1 Got:
java.io.EOFException
at java.io.DataInputStream.readFully(DataInputStream.java:180)
at java.io.DataInputStream.readFully(DataInputStream.java:152)
at org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1508)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1486)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1475)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1470)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader$WALReader.init(SequenceFileLogReader.java:55)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader.init(SequenceFileLogReader.java:175)
at
org.apache.hadoop.hbase.regionserver.wal.HLog.getReader(HLog.java:716)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.openReader(ReplicationSource.java:491)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.run(ReplicationSource.java:290)
2012-11-07 15:47:40,927 WARN regionserver.ReplicationSource
(ReplicationSource.java:openReader(547)) - Waited too long for this file,
considering dumping
2012-11-07 15:47:40,927 DEBUG regionserver.ReplicationSource
(ReplicationSource.java:sleepForRetries(562)) - Unable to open a reader,
sleeping 1000 times 10
{code}
We should reduce the log spewing in this case (or some informative message,
based on the offset).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-7122) Proper warning message when opening a log file with no entries (idle cluster)
[
https://issues.apache.org/jira/browse/HBASE-7122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13562738#comment-13562738
]
Hadoop QA commented on HBASE-7122:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12566508/HBASE-7122.v2.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 hadoop2.0{color}. The patch compiles against the hadoop
2.0 profile.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.regionserver.wal.TestHLog
{color:red}-1 core zombie tests{color}. There are 1 zombie test(s):
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/4180//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4180//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4180//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4180//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4180//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4180//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4180//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/4180//console
This message is automatically generated.
Proper warning message when opening a log file with no entries (idle cluster)
-
Key: HBASE-7122
URL: https://issues.apache.org/jira/browse/HBASE-7122
Project: HBase
Issue Type: Sub-task
Components: Replication
Affects Versions: 0.94.2
Reporter: Himanshu Vashishtha
Assignee: Himanshu Vashishtha
Fix For: 0.96.0
Attachments: HBase-7122.patch, HBASE-7122.v2.patch
In case the cluster is idle and the log has rolled (offset to 0),
replicationSource tries to open the log and gets an EOF exception. This gets
printed after every 10 sec until an entry is inserted in it.
{code}
2012-11-07 15:47:40,924 DEBUG regionserver.ReplicationSource
(ReplicationSource.java:openReader(487)) - Opening log for replication
c0315.hal.cloudera.com%2C40020%2C1352324202860.1352327804874 at 0
2012-11-07 15:47:40,926 WARN regionserver.ReplicationSource
(ReplicationSource.java:openReader(543)) - 1 Got:
java.io.EOFException
at java.io.DataInputStream.readFully(DataInputStream.java:180)
at java.io.DataInputStream.readFully(DataInputStream.java:152)
at org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1508)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1486)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1475)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1470)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader$WALReader.init(SequenceFileLogReader.java:55)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader.init(SequenceFileLogReader.java:175)
at
org.apache.hadoop.hbase.regionserver.wal.HLog.getReader(HLog.java:716)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.openReader(ReplicationSource.java:491)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.run(ReplicationSource.java:290)
2012-11-07 15:47:40,927 WARN regionserver.ReplicationSource
[jira] [Commented] (HBASE-7122) Proper warning message when opening a log file with no entries (idle cluster)
[
https://issues.apache.org/jira/browse/HBASE-7122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13550938#comment-13550938
]
stack commented on HBASE-7122:
--
+1 on patch. Looking at HBASE-6804, I do not see this patch rolled in there.
Is that so Himanshu? Can you make a trunk patch? Thanks boss.
Proper warning message when opening a log file with no entries (idle cluster)
-
Key: HBASE-7122
URL: https://issues.apache.org/jira/browse/HBASE-7122
Project: HBase
Issue Type: Sub-task
Components: Replication
Affects Versions: 0.94.2
Reporter: Himanshu Vashishtha
Assignee: Himanshu Vashishtha
Fix For: 0.96.0
Attachments: HBase-7122.patch
In case the cluster is idle and the log has rolled (offset to 0),
replicationSource tries to open the log and gets an EOF exception. This gets
printed after every 10 sec until an entry is inserted in it.
{code}
2012-11-07 15:47:40,924 DEBUG regionserver.ReplicationSource
(ReplicationSource.java:openReader(487)) - Opening log for replication
c0315.hal.cloudera.com%2C40020%2C1352324202860.1352327804874 at 0
2012-11-07 15:47:40,926 WARN regionserver.ReplicationSource
(ReplicationSource.java:openReader(543)) - 1 Got:
java.io.EOFException
at java.io.DataInputStream.readFully(DataInputStream.java:180)
at java.io.DataInputStream.readFully(DataInputStream.java:152)
at org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1508)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1486)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1475)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1470)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader$WALReader.init(SequenceFileLogReader.java:55)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader.init(SequenceFileLogReader.java:175)
at
org.apache.hadoop.hbase.regionserver.wal.HLog.getReader(HLog.java:716)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.openReader(ReplicationSource.java:491)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.run(ReplicationSource.java:290)
2012-11-07 15:47:40,927 WARN regionserver.ReplicationSource
(ReplicationSource.java:openReader(547)) - Waited too long for this file,
considering dumping
2012-11-07 15:47:40,927 DEBUG regionserver.ReplicationSource
(ReplicationSource.java:sleepForRetries(562)) - Unable to open a reader,
sleeping 1000 times 10
{code}
We should reduce the log spewing in this case (or some informative message,
based on the offset).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-7122) Proper warning message when opening a log file with no entries (idle cluster)
[
https://issues.apache.org/jira/browse/HBASE-7122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13493645#comment-13493645
]
Hadoop QA commented on HBASE-7122:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12552737/HBase-7122.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/3279//console
This message is automatically generated.
Proper warning message when opening a log file with no entries (idle cluster)
-
Key: HBASE-7122
URL: https://issues.apache.org/jira/browse/HBASE-7122
Project: HBase
Issue Type: Sub-task
Components: Replication
Affects Versions: 0.94.2
Reporter: Himanshu Vashishtha
Assignee: Himanshu Vashishtha
Fix For: 0.96.0
Attachments: HBase-7122.patch
In case the cluster is idle and the log has rolled (offset to 0),
replicationSource tries to open the log and gets an EOF exception. This gets
printed after every 10 sec until an entry is inserted in it.
{code}
2012-11-07 15:47:40,924 DEBUG regionserver.ReplicationSource
(ReplicationSource.java:openReader(487)) - Opening log for replication
c0315.hal.cloudera.com%2C40020%2C1352324202860.1352327804874 at 0
2012-11-07 15:47:40,926 WARN regionserver.ReplicationSource
(ReplicationSource.java:openReader(543)) - 1 Got:
java.io.EOFException
at java.io.DataInputStream.readFully(DataInputStream.java:180)
at java.io.DataInputStream.readFully(DataInputStream.java:152)
at org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1508)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1486)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1475)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1470)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader$WALReader.init(SequenceFileLogReader.java:55)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader.init(SequenceFileLogReader.java:175)
at
org.apache.hadoop.hbase.regionserver.wal.HLog.getReader(HLog.java:716)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.openReader(ReplicationSource.java:491)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.run(ReplicationSource.java:290)
2012-11-07 15:47:40,927 WARN regionserver.ReplicationSource
(ReplicationSource.java:openReader(547)) - Waited too long for this file,
considering dumping
2012-11-07 15:47:40,927 DEBUG regionserver.ReplicationSource
(ReplicationSource.java:sleepForRetries(562)) - Unable to open a reader,
sleeping 1000 times 10
{code}
We should reduce the log spewing in this case (or some informative message,
based on the offset).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-7122) Proper warning message when opening a log file with no entries (idle cluster)
[
https://issues.apache.org/jira/browse/HBASE-7122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13492888#comment-13492888
]
Jean-Daniel Cryans commented on HBASE-7122:
---
We could fold this in HBASE-6804.
Proper warning message when opening a log file with no entries (idle cluster)
-
Key: HBASE-7122
URL: https://issues.apache.org/jira/browse/HBASE-7122
Project: HBase
Issue Type: Bug
Components: Replication
Affects Versions: 0.94.2
Reporter: Himanshu Vashishtha
Assignee: Himanshu Vashishtha
Fix For: 0.96.0
In case the cluster is idle and the log has rolled (offset to 0),
replicationSource tries to open the log and gets an EOF exception. This gets
printed after every 10 sec until an entry is inserted in it.
{code}
2012-11-07 15:47:40,924 DEBUG regionserver.ReplicationSource
(ReplicationSource.java:openReader(487)) - Opening log for replication
c0315.hal.cloudera.com%2C40020%2C1352324202860.1352327804874 at 0
2012-11-07 15:47:40,926 WARN regionserver.ReplicationSource
(ReplicationSource.java:openReader(543)) - 1 Got:
java.io.EOFException
at java.io.DataInputStream.readFully(DataInputStream.java:180)
at java.io.DataInputStream.readFully(DataInputStream.java:152)
at org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1508)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1486)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1475)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1470)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader$WALReader.init(SequenceFileLogReader.java:55)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader.init(SequenceFileLogReader.java:175)
at
org.apache.hadoop.hbase.regionserver.wal.HLog.getReader(HLog.java:716)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.openReader(ReplicationSource.java:491)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.run(ReplicationSource.java:290)
2012-11-07 15:47:40,927 WARN regionserver.ReplicationSource
(ReplicationSource.java:openReader(547)) - Waited too long for this file,
considering dumping
2012-11-07 15:47:40,927 DEBUG regionserver.ReplicationSource
(ReplicationSource.java:sleepForRetries(562)) - Unable to open a reader,
sleeping 1000 times 10
{code}
We should reduce the log spewing in this case (or some informative message,
based on the offset).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
