[jira] [Commented] (HBASE-18623) Frequent failed to parse at EOF warnings from WALEntryStream
[
https://issues.apache.org/jira/browse/HBASE-18623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16137337#comment-16137337
]
Hudson commented on HBASE-18623:
FAILURE: Integrated in Jenkins build HBASE-14070.HLC #263 (See
[https://builds.apache.org/job/HBASE-14070.HLC/263/])
HBASE-18623 Frequent failed to parse at EOF warnings from WALEntryStream
(apurtell: rev 70d48b113e3b824e2804164e80edf01522c85272)
* (edit)
hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/WALEntryStream.java
> Frequent failed to parse at EOF warnings from WALEntryStream
>
>
> Key: HBASE-18623
> URL: https://issues.apache.org/jira/browse/HBASE-18623
> Project: HBase
> Issue Type: Task
>Reporter: Andrew Purtell
>Assignee: Andrew Purtell
>Priority: Minor
> Fix For: 2.0.0, 3.0.0, 1.4.0, 1.5.0
>
> Attachments: HBASE-18623.patch
>
>
> Lots of messages like this
> {noformat}
> 2017-08-17 15:10:36,363 INFO
> [main-EventThread.replicationSource,2.replicationSource.replicationWALReaderThread.onyx%2C8120%2C1503007587035,2]
> regionserver.WALEntryStream: Reached the end of WAL file
> 'hdfs://localhost:8020/hbase-1/WALs/onyx,8120,1503007587035/onyx%2C8120%2C1503007587035.1503007826083'.
> It was not closed cleanly, so we did not parse 8 bytes of data.
> {noformat}
> Fix this, either the message (if harmless) or the underlying cause.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18623) Frequent failed to parse at EOF warnings from WALEntryStream
[
https://issues.apache.org/jira/browse/HBASE-18623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16135878#comment-16135878
]
Hudson commented on HBASE-18623:
FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #3572 (See
[https://builds.apache.org/job/HBase-Trunk_matrix/3572/])
HBASE-18623 Frequent failed to parse at EOF warnings from WALEntryStream
(apurtell: rev 70d48b113e3b824e2804164e80edf01522c85272)
* (edit)
hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/WALEntryStream.java
> Frequent failed to parse at EOF warnings from WALEntryStream
>
>
> Key: HBASE-18623
> URL: https://issues.apache.org/jira/browse/HBASE-18623
> Project: HBase
> Issue Type: Task
>Reporter: Andrew Purtell
>Assignee: Andrew Purtell
>Priority: Minor
> Fix For: 2.0.0, 3.0.0, 1.4.0, 1.5.0
>
> Attachments: HBASE-18623.patch
>
>
> Lots of messages like this
> {noformat}
> 2017-08-17 15:10:36,363 INFO
> [main-EventThread.replicationSource,2.replicationSource.replicationWALReaderThread.onyx%2C8120%2C1503007587035,2]
> regionserver.WALEntryStream: Reached the end of WAL file
> 'hdfs://localhost:8020/hbase-1/WALs/onyx,8120,1503007587035/onyx%2C8120%2C1503007587035.1503007826083'.
> It was not closed cleanly, so we did not parse 8 bytes of data.
> {noformat}
> Fix this, either the message (if harmless) or the underlying cause.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18623) Frequent failed to parse at EOF warnings from WALEntryStream
[
https://issues.apache.org/jira/browse/HBASE-18623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16135742#comment-16135742
]
Hudson commented on HBASE-18623:
FAILURE: Integrated in Jenkins build HBase-2.0 #371 (See
[https://builds.apache.org/job/HBase-2.0/371/])
HBASE-18623 Frequent failed to parse at EOF warnings from WALEntryStream
(apurtell: rev 7fef60634952135a063493051220a83308d04e22)
* (edit)
hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/WALEntryStream.java
> Frequent failed to parse at EOF warnings from WALEntryStream
>
>
> Key: HBASE-18623
> URL: https://issues.apache.org/jira/browse/HBASE-18623
> Project: HBase
> Issue Type: Task
>Reporter: Andrew Purtell
>Assignee: Andrew Purtell
>Priority: Minor
> Fix For: 2.0.0, 3.0.0, 1.4.0, 1.5.0
>
> Attachments: HBASE-18623.patch
>
>
> Lots of messages like this
> {noformat}
> 2017-08-17 15:10:36,363 INFO
> [main-EventThread.replicationSource,2.replicationSource.replicationWALReaderThread.onyx%2C8120%2C1503007587035,2]
> regionserver.WALEntryStream: Reached the end of WAL file
> 'hdfs://localhost:8020/hbase-1/WALs/onyx,8120,1503007587035/onyx%2C8120%2C1503007587035.1503007826083'.
> It was not closed cleanly, so we did not parse 8 bytes of data.
> {noformat}
> Fix this, either the message (if harmless) or the underlying cause.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18623) Frequent failed to parse at EOF warnings from WALEntryStream
[
https://issues.apache.org/jira/browse/HBASE-18623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16135603#comment-16135603
]
Hudson commented on HBASE-18623:
FAILURE: Integrated in Jenkins build HBase-1.4 #873 (See
[https://builds.apache.org/job/HBase-1.4/873/])
HBASE-18623 Frequent failed to parse at EOF warnings from WALEntryStream
(apurtell: rev c51c784697b1dc108e7ad31fdae7992b754c9430)
* (edit)
hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/WALEntryStream.java
> Frequent failed to parse at EOF warnings from WALEntryStream
>
>
> Key: HBASE-18623
> URL: https://issues.apache.org/jira/browse/HBASE-18623
> Project: HBase
> Issue Type: Task
>Reporter: Andrew Purtell
>Assignee: Andrew Purtell
>Priority: Minor
> Fix For: 2.0.0, 3.0.0, 1.4.0, 1.5.0
>
> Attachments: HBASE-18623.patch
>
>
> Lots of messages like this
> {noformat}
> 2017-08-17 15:10:36,363 INFO
> [main-EventThread.replicationSource,2.replicationSource.replicationWALReaderThread.onyx%2C8120%2C1503007587035,2]
> regionserver.WALEntryStream: Reached the end of WAL file
> 'hdfs://localhost:8020/hbase-1/WALs/onyx,8120,1503007587035/onyx%2C8120%2C1503007587035.1503007826083'.
> It was not closed cleanly, so we did not parse 8 bytes of data.
> {noformat}
> Fix this, either the message (if harmless) or the underlying cause.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18623) Frequent failed to parse at EOF warnings from WALEntryStream
[
https://issues.apache.org/jira/browse/HBASE-18623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16135580#comment-16135580
]
Hudson commented on HBASE-18623:
FAILURE: Integrated in Jenkins build HBase-1.5 #20 (See
[https://builds.apache.org/job/HBase-1.5/20/])
HBASE-18623 Frequent failed to parse at EOF warnings from WALEntryStream
(apurtell: rev 19fffacd3a95bc6eebd3ea3bc0d9ff0a2593e37b)
* (edit)
hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/WALEntryStream.java
> Frequent failed to parse at EOF warnings from WALEntryStream
>
>
> Key: HBASE-18623
> URL: https://issues.apache.org/jira/browse/HBASE-18623
> Project: HBase
> Issue Type: Task
>Reporter: Andrew Purtell
>Assignee: Andrew Purtell
>Priority: Minor
> Fix For: 2.0.0, 3.0.0, 1.4.0, 1.5.0
>
> Attachments: HBASE-18623.patch
>
>
> Lots of messages like this
> {noformat}
> 2017-08-17 15:10:36,363 INFO
> [main-EventThread.replicationSource,2.replicationSource.replicationWALReaderThread.onyx%2C8120%2C1503007587035,2]
> regionserver.WALEntryStream: Reached the end of WAL file
> 'hdfs://localhost:8020/hbase-1/WALs/onyx,8120,1503007587035/onyx%2C8120%2C1503007587035.1503007826083'.
> It was not closed cleanly, so we did not parse 8 bytes of data.
> {noformat}
> Fix this, either the message (if harmless) or the underlying cause.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18623) Frequent failed to parse at EOF warnings from WALEntryStream
[
https://issues.apache.org/jira/browse/HBASE-18623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16133935#comment-16133935
]
Sean Busbey commented on HBASE-18623:
-
+1.
> Frequent failed to parse at EOF warnings from WALEntryStream
>
>
> Key: HBASE-18623
> URL: https://issues.apache.org/jira/browse/HBASE-18623
> Project: HBase
> Issue Type: Task
>Reporter: Andrew Purtell
>Assignee: Andrew Purtell
>Priority: Minor
> Fix For: 2.0.0, 3.0.0, 1.4.0, 1.5.0
>
> Attachments: HBASE-18623.patch
>
>
> Lots of messages like this
> {noformat}
> 2017-08-17 15:10:36,363 INFO
> [main-EventThread.replicationSource,2.replicationSource.replicationWALReaderThread.onyx%2C8120%2C1503007587035,2]
> regionserver.WALEntryStream: Reached the end of WAL file
> 'hdfs://localhost:8020/hbase-1/WALs/onyx,8120,1503007587035/onyx%2C8120%2C1503007587035.1503007826083'.
> It was not closed cleanly, so we did not parse 8 bytes of data.
> {noformat}
> Fix this, either the message (if harmless) or the underlying cause.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18623) Frequent failed to parse at EOF warnings from WALEntryStream
[
https://issues.apache.org/jira/browse/HBASE-18623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16133926#comment-16133926
]
Hadoop QA commented on HBASE-18623:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
24s{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m
0s{color} | {color:red} 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} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
15s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
42s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
51s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
16s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 3m
36s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
36s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
54s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
46s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
46s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
54s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
16s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
38m 27s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 4m
12s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
36s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green}145m
30s{color} | {color:green} hbase-server in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
20s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}202m 53s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:bdc94b1 |
| JIRA Issue | HBASE-18623 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12882695/HBASE-18623.patch |
| Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck
hbaseanti checkstyle compile |
| uname | Linux 4033d28d9340 3.13.0-116-generic #163-Ubuntu SMP Fri Mar 31
14:13:22 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
|
| git revision | master / b932d38 |
| Default Java | 1.8.0_144 |
| findbugs | v3.1.0-RC3 |
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/8171/testReport/ |
| modules | C: hbase-server U: hbase-server |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/8171/console |
| Powered by | Apache Yetus 0.4.0 http://yetus.apache.org |
This message was automatically generated.
> Frequent failed to parse at EOF warnings from WALEntryStream
>
>
> Key: HBASE-18623
> URL: https://issues.apache.org/jira/browse/HBASE-18623
> Project: HBase
> Issue Type: Task
>Reporter: Andrew Purtell
>Assignee:
[jira] [Commented] (HBASE-18623) Frequent failed to parse at EOF warnings from WALEntryStream
[
https://issues.apache.org/jira/browse/HBASE-18623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16133826#comment-16133826
]
Andrew Purtell commented on HBASE-18623:
Going to commit trivial patch implementing Sean's suggestion, a logging only
change, tomorrow unless objection.
> Frequent failed to parse at EOF warnings from WALEntryStream
>
>
> Key: HBASE-18623
> URL: https://issues.apache.org/jira/browse/HBASE-18623
> Project: HBase
> Issue Type: Task
>Reporter: Andrew Purtell
>Assignee: Andrew Purtell
>Priority: Minor
> Fix For: 2.0.0, 3.0.0, 1.4.0, 1.5.0
>
> Attachments: HBASE-18623.patch
>
>
> Lots of messages like this
> {noformat}
> 2017-08-17 15:10:36,363 INFO
> [main-EventThread.replicationSource,2.replicationSource.replicationWALReaderThread.onyx%2C8120%2C1503007587035,2]
> regionserver.WALEntryStream: Reached the end of WAL file
> 'hdfs://localhost:8020/hbase-1/WALs/onyx,8120,1503007587035/onyx%2C8120%2C1503007587035.1503007826083'.
> It was not closed cleanly, so we did not parse 8 bytes of data.
> {noformat}
> Fix this, either the message (if harmless) or the underlying cause.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18623) Frequent failed to parse at EOF warnings from WALEntryStream
[
https://issues.apache.org/jira/browse/HBASE-18623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16133579#comment-16133579
]
Andrew Purtell commented on HBASE-18623:
Ok [~busbey] I'll implement that suggestion.
> Frequent failed to parse at EOF warnings from WALEntryStream
>
>
> Key: HBASE-18623
> URL: https://issues.apache.org/jira/browse/HBASE-18623
> Project: HBase
> Issue Type: Task
>Reporter: Andrew Purtell
> Fix For: 1.4.0, 1.5.0
>
>
> Lots of messages like this
> {noformat}
> 2017-08-17 15:10:36,363 INFO
> [main-EventThread.replicationSource,2.replicationSource.replicationWALReaderThread.onyx%2C8120%2C1503007587035,2]
> regionserver.WALEntryStream: Reached the end of WAL file
> 'hdfs://localhost:8020/hbase-1/WALs/onyx,8120,1503007587035/onyx%2C8120%2C1503007587035.1503007826083'.
> It was not closed cleanly, so we did not parse 8 bytes of data.
> {noformat}
> Fix this, either the message (if harmless) or the underlying cause.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18623) Frequent failed to parse at EOF warnings from WALEntryStream
[
https://issues.apache.org/jira/browse/HBASE-18623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16131578#comment-16131578
]
Sean Busbey commented on HBASE-18623:
-
IIRC, this was added back when I was trying to get more information out of the
replication system. The situation described is *probably* harmless, since we
expect non-cleanly closed WALs to have unparseable partial entries. It's hard
to say it's always fine, since we have yet to find the source of the corruption
in HBASE-15983.
How about we move the message to DEBUG and expressly have it say that the
failure to parse some data in an unclosed file is usually fine?
> Frequent failed to parse at EOF warnings from WALEntryStream
>
>
> Key: HBASE-18623
> URL: https://issues.apache.org/jira/browse/HBASE-18623
> Project: HBase
> Issue Type: Task
>Reporter: Andrew Purtell
> Fix For: 1.4.0, 1.5.0
>
>
> Lots of messages like this
> {noformat}
> 2017-08-17 15:10:36,363 INFO
> [main-EventThread.replicationSource,2.replicationSource.replicationWALReaderThread.onyx%2C8120%2C1503007587035,2]
> regionserver.WALEntryStream: Reached the end of WAL file
> 'hdfs://localhost:8020/hbase-1/WALs/onyx,8120,1503007587035/onyx%2C8120%2C1503007587035.1503007826083'.
> It was not closed cleanly, so we did not parse 8 bytes of data.
> {noformat}
> Fix this, either the message (if harmless) or the underlying cause.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
