[jira] [Commented] (HBASE-20145) HMaster start fails with IllegalStateException when HADOOP_HOME is set
[ https://issues.apache.org/jira/browse/HBASE-20145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16578664#comment-16578664 ] stack commented on HBASE-20145: --- What to do here? There are outstanding comments up in RB. Would be good to address. I like the idea of improving the logging hereabouts. Otherwise, we resolve this as not-a-problem because it is the old classic of mixed jars on CLASSPATH (but hopefully the improved logging will help user figure the problem easier?) > HMaster start fails with IllegalStateException when HADOOP_HOME is set > -- > > Key: HBASE-20145 > URL: https://issues.apache.org/jira/browse/HBASE-20145 > Project: HBase > Issue Type: Sub-task > Components: wal >Affects Versions: 2.0.0-beta-1 > Environment: HBase-2.0-beta1. > Hadoop trunk version. > java version "1.8.0_144" >Reporter: Rohith Sharma K S >Assignee: Wei-Chiu Chuang >Priority: Major > Attachments: HBASE-20145.master.001.patch > > > It is observed that HMaster start is failed when HADOOP_HOME is set as env > while starting HMaster. HADOOP_HOME is pointing to Hadoop trunk version. > {noformat} > 2018-03-07 16:59:52,654 ERROR [master//10.200.4.200:16000] master.HMaster: > Failed to become active master > java.lang.IllegalStateException: The procedure WAL relies on the ability to > hsync for proper operation during component failures, but the underlying > filesystem does not support doing so. Please check the config value of > 'hbase.procedure.store.wal.use.hsync' to set the desired level of robustness > and ensure the config value of 'hbase.wal.dir' points to a FileSystem mount > that can provide it. > at > org.apache.hadoop.hbase.procedure2.store.wal.WALProcedureStore.rollWriter(WALProcedureStore.java:1036) > at > org.apache.hadoop.hbase.procedure2.store.wal.WALProcedureStore.recoverLease(WALProcedureStore.java:374) > at > org.apache.hadoop.hbase.procedure2.ProcedureExecutor.start(ProcedureExecutor.java:532) > at > org.apache.hadoop.hbase.master.HMaster.startProcedureExecutor(HMaster.java:1232) > at > org.apache.hadoop.hbase.master.HMaster.startServiceThreads(HMaster.java:1145) > at > org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(HMaster.java:837) > at > org.apache.hadoop.hbase.master.HMaster.startActiveMasterManager(HMaster.java:2026) > at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:547) > at java.lang.Thread.run(Thread.java:748) > {noformat} > The same configs is working in HBase-1.2.6 build properly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-20145) HMaster start fails with IllegalStateException when HADOOP_HOME is set
[ https://issues.apache.org/jira/browse/HBASE-20145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16563866#comment-16563866 ] Sean Busbey commented on HBASE-20145: - IIRC all of the server processes still get the classpath they always did. so probably this same error will happen if you point HADOOP_HOME somewhere and don't remove the hadoop jars that ship with your hbase installation. > HMaster start fails with IllegalStateException when HADOOP_HOME is set > -- > > Key: HBASE-20145 > URL: https://issues.apache.org/jira/browse/HBASE-20145 > Project: HBase > Issue Type: Sub-task > Components: wal >Affects Versions: 2.0.0-beta-1 > Environment: HBase-2.0-beta1. > Hadoop trunk version. > java version "1.8.0_144" >Reporter: Rohith Sharma K S >Assignee: Wei-Chiu Chuang >Priority: Major > Attachments: HBASE-20145.master.001.patch > > > It is observed that HMaster start is failed when HADOOP_HOME is set as env > while starting HMaster. HADOOP_HOME is pointing to Hadoop trunk version. > {noformat} > 2018-03-07 16:59:52,654 ERROR [master//10.200.4.200:16000] master.HMaster: > Failed to become active master > java.lang.IllegalStateException: The procedure WAL relies on the ability to > hsync for proper operation during component failures, but the underlying > filesystem does not support doing so. Please check the config value of > 'hbase.procedure.store.wal.use.hsync' to set the desired level of robustness > and ensure the config value of 'hbase.wal.dir' points to a FileSystem mount > that can provide it. > at > org.apache.hadoop.hbase.procedure2.store.wal.WALProcedureStore.rollWriter(WALProcedureStore.java:1036) > at > org.apache.hadoop.hbase.procedure2.store.wal.WALProcedureStore.recoverLease(WALProcedureStore.java:374) > at > org.apache.hadoop.hbase.procedure2.ProcedureExecutor.start(ProcedureExecutor.java:532) > at > org.apache.hadoop.hbase.master.HMaster.startProcedureExecutor(HMaster.java:1232) > at > org.apache.hadoop.hbase.master.HMaster.startServiceThreads(HMaster.java:1145) > at > org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(HMaster.java:837) > at > org.apache.hadoop.hbase.master.HMaster.startActiveMasterManager(HMaster.java:2026) > at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:547) > at java.lang.Thread.run(Thread.java:748) > {noformat} > The same configs is working in HBase-1.2.6 build properly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-20145) HMaster start fails with IllegalStateException when HADOOP_HOME is set
[ https://issues.apache.org/jira/browse/HBASE-20145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16562166#comment-16562166 ] Hadoop QA commented on HBASE-20145: --- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem || Runtime || Comment || | {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 11s{color} | {color:blue} Docker mode activated. {color} | || || || || {color:brown} Prechecks {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:orange}-0{color} | {color:orange} test4tests {color} | {color:orange} 0m 0s{color} | {color:orange} 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:brown} master Compile Tests {color} || | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m 41s{color} | {color:green} master passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 27s{color} | {color:green} master passed {color} | | {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m 22s{color} | {color:green} master passed {color} | | {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 4m 31s{color} | {color:green} branch has no errors when building our shaded downstream artifacts. {color} | | {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m 39s{color} | {color:green} master passed {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 18s{color} | {color:green} master passed {color} | || || || || {color:brown} Patch Compile Tests {color} || | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m 56s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 29s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 29s{color} | {color:green} the patch passed {color} | | {color:red}-1{color} | {color:red} checkstyle {color} | {color:red} 0m 22s{color} | {color:red} hbase-common: The patch generated 1 new + 3 unchanged - 0 fixed = 4 total (was 3) {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} shadedjars {color} | {color:green} 4m 40s{color} | {color:green} patch has no errors when building our shaded downstream artifacts. {color} | | {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green} 10m 27s{color} | {color:green} Patch does not cause any errors with Hadoop 2.7.4 or 3.0.0. {color} | | {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m 45s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 18s{color} | {color:green} the patch passed {color} | || || || || {color:brown} Other Tests {color} || | {color:green}+1{color} | {color:green} unit {color} | {color:green} 2m 27s{color} | {color:green} hbase-common in the patch passed. {color} | | {color:green}+1{color} | {color:green} unit {color} | {color:green}128m 15s{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}164m 35s{color} | {color:black} {color} | \\ \\ || Subsystem || Report/Notes || | Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:b002b0b | | JIRA Issue | HBASE-20145 | | JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12918983/HBASE-20145.master.001.patch | | Optional Tests | asflicense javac javadoc unit findbugs shadedjars hadoopcheck hbaseanti checkstyle compile | | uname | Linux 3b5838ebdec8 3.13.0-143-generic #192-Ubuntu SMP Tue Feb 27 10:45:36 UTC 2018 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 / c075f33fc7 | | maven | version: Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe; 2018-06-17T18:33:14Z) | | Default Java | 1.8.0_171 | | findbugs | v3.1.0-RC3 | | checkstyle |
[jira] [Commented] (HBASE-20145) HMaster start fails with IllegalStateException when HADOOP_HOME is set
[ https://issues.apache.org/jira/browse/HBASE-20145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16561966#comment-16561966 ] Mike Drob commented on HBASE-20145: --- I *think* this is something that gets addressed via the bring-your-own hadoop clients that we make now. [~busbey] WDYT? > HMaster start fails with IllegalStateException when HADOOP_HOME is set > -- > > Key: HBASE-20145 > URL: https://issues.apache.org/jira/browse/HBASE-20145 > Project: HBase > Issue Type: Sub-task > Components: wal >Affects Versions: 2.0.0-beta-1 > Environment: HBase-2.0-beta1. > Hadoop trunk version. > java version "1.8.0_144" >Reporter: Rohith Sharma K S >Assignee: Wei-Chiu Chuang >Priority: Major > Attachments: HBASE-20145.master.001.patch > > > It is observed that HMaster start is failed when HADOOP_HOME is set as env > while starting HMaster. HADOOP_HOME is pointing to Hadoop trunk version. > {noformat} > 2018-03-07 16:59:52,654 ERROR [master//10.200.4.200:16000] master.HMaster: > Failed to become active master > java.lang.IllegalStateException: The procedure WAL relies on the ability to > hsync for proper operation during component failures, but the underlying > filesystem does not support doing so. Please check the config value of > 'hbase.procedure.store.wal.use.hsync' to set the desired level of robustness > and ensure the config value of 'hbase.wal.dir' points to a FileSystem mount > that can provide it. > at > org.apache.hadoop.hbase.procedure2.store.wal.WALProcedureStore.rollWriter(WALProcedureStore.java:1036) > at > org.apache.hadoop.hbase.procedure2.store.wal.WALProcedureStore.recoverLease(WALProcedureStore.java:374) > at > org.apache.hadoop.hbase.procedure2.ProcedureExecutor.start(ProcedureExecutor.java:532) > at > org.apache.hadoop.hbase.master.HMaster.startProcedureExecutor(HMaster.java:1232) > at > org.apache.hadoop.hbase.master.HMaster.startServiceThreads(HMaster.java:1145) > at > org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(HMaster.java:837) > at > org.apache.hadoop.hbase.master.HMaster.startActiveMasterManager(HMaster.java:2026) > at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:547) > at java.lang.Thread.run(Thread.java:748) > {noformat} > The same configs is working in HBase-1.2.6 build properly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-20145) HMaster start fails with IllegalStateException when HADOOP_HOME is set
[ https://issues.apache.org/jira/browse/HBASE-20145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16438402#comment-16438402 ] Mike Drob commented on HBASE-20145: --- posted comments on reviewboard > HMaster start fails with IllegalStateException when HADOOP_HOME is set > -- > > Key: HBASE-20145 > URL: https://issues.apache.org/jira/browse/HBASE-20145 > Project: HBase > Issue Type: Bug > Components: wal >Affects Versions: 2.0.0-beta-1 > Environment: HBase-2.0-beta1. > Hadoop trunk version. > java version "1.8.0_144" >Reporter: Rohith Sharma K S >Assignee: Wei-Chiu Chuang >Priority: Major > Attachments: HBASE-20145.master.001.patch > > > It is observed that HMaster start is failed when HADOOP_HOME is set as env > while starting HMaster. HADOOP_HOME is pointing to Hadoop trunk version. > {noformat} > 2018-03-07 16:59:52,654 ERROR [master//10.200.4.200:16000] master.HMaster: > Failed to become active master > java.lang.IllegalStateException: The procedure WAL relies on the ability to > hsync for proper operation during component failures, but the underlying > filesystem does not support doing so. Please check the config value of > 'hbase.procedure.store.wal.use.hsync' to set the desired level of robustness > and ensure the config value of 'hbase.wal.dir' points to a FileSystem mount > that can provide it. > at > org.apache.hadoop.hbase.procedure2.store.wal.WALProcedureStore.rollWriter(WALProcedureStore.java:1036) > at > org.apache.hadoop.hbase.procedure2.store.wal.WALProcedureStore.recoverLease(WALProcedureStore.java:374) > at > org.apache.hadoop.hbase.procedure2.ProcedureExecutor.start(ProcedureExecutor.java:532) > at > org.apache.hadoop.hbase.master.HMaster.startProcedureExecutor(HMaster.java:1232) > at > org.apache.hadoop.hbase.master.HMaster.startServiceThreads(HMaster.java:1145) > at > org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(HMaster.java:837) > at > org.apache.hadoop.hbase.master.HMaster.startActiveMasterManager(HMaster.java:2026) > at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:547) > at java.lang.Thread.run(Thread.java:748) > {noformat} > The same configs is working in HBase-1.2.6 build properly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-20145) HMaster start fails with IllegalStateException when HADOOP_HOME is set
[ https://issues.apache.org/jira/browse/HBASE-20145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16438158#comment-16438158 ] Hadoop QA commented on HBASE-20145: --- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem || Runtime || Comment || | {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 16s{color} | {color:blue} Docker mode activated. {color} | || || || || {color:brown} Prechecks {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:brown} master Compile Tests {color} || | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m 7s{color} | {color:green} master passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 26s{color} | {color:green} master passed {color} | | {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m 22s{color} | {color:green} master passed {color} | | {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 4m 17s{color} | {color:green} branch has no errors when building our shaded downstream artifacts. {color} | | {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m 31s{color} | {color:green} master passed {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 16s{color} | {color:green} master passed {color} | || || || || {color:brown} Patch Compile Tests {color} || | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m 9s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 26s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 26s{color} | {color:green} the patch passed {color} | | {color:red}-1{color} | {color:red} checkstyle {color} | {color:red} 0m 22s{color} | {color:red} hbase-common: The patch generated 1 new + 1 unchanged - 0 fixed = 2 total (was 1) {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} shadedjars {color} | {color:green} 4m 13s{color} | {color:green} patch has no errors when building our shaded downstream artifacts. {color} | | {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green} 13m 2s{color} | {color:green} Patch does not cause any errors with Hadoop 2.6.5 2.7.4 or 3.0.0. {color} | | {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m 38s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 15s{color} | {color:green} the patch passed {color} | || || || || {color:brown} Other Tests {color} || | {color:green}+1{color} | {color:green} unit {color} | {color:green} 2m 27s{color} | {color:green} hbase-common in the patch passed. {color} | | {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m 9s{color} | {color:green} The patch does not generate ASF License warnings. {color} | | {color:black}{color} | {color:black} {color} | {color:black} 36m 22s{color} | {color:black} {color} | \\ \\ || Subsystem || Report/Notes || | Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:d8b550f | | JIRA Issue | HBASE-20145 | | JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12918983/HBASE-20145.master.001.patch | | Optional Tests | asflicense javac javadoc unit findbugs shadedjars hadoopcheck hbaseanti checkstyle compile | | uname | Linux def60d3fb016 4.4.0-43-generic #63-Ubuntu SMP Wed Oct 12 13:48:03 UTC 2016 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 / 73275f1774 | | maven | version: Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T19:49:05Z) | | Default Java | 1.8.0_162 | | findbugs | v3.1.0-RC3 | | checkstyle | https://builds.apache.org/job/PreCommit-HBASE-Build/12446/artifact/patchprocess/diff-checkstyle-hbase-common.txt | | Test Results | https://builds.apache.org/job/PreCommit-HBASE-Build/12446/testReport/ | | Max.
[jira] [Commented] (HBASE-20145) HMaster start fails with IllegalStateException when HADOOP_HOME is set
[ https://issues.apache.org/jira/browse/HBASE-20145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16437675#comment-16437675 ] Wei-Chiu Chuang commented on HBASE-20145: - Posted a patch to log additional messages when 1. the stream class does not implement StreamCapabilities, 2. the result of StreamCapabilities test. Log the output stream class and the associated wrapped stream class. The 2nd item will be useful when troubleshooting hbase problem on a HDFS erasure coded cluster. > HMaster start fails with IllegalStateException when HADOOP_HOME is set > -- > > Key: HBASE-20145 > URL: https://issues.apache.org/jira/browse/HBASE-20145 > Project: HBase > Issue Type: Bug > Environment: HBase-2.0-beta1. > Hadoop trunk version. > java version "1.8.0_144" >Reporter: Rohith Sharma K S >Assignee: Wei-Chiu Chuang >Priority: Critical > Attachments: HBASE-20145.master.001.patch > > > It is observed that HMaster start is failed when HADOOP_HOME is set as env > while starting HMaster. HADOOP_HOME is pointing to Hadoop trunk version. > {noformat} > 2018-03-07 16:59:52,654 ERROR [master//10.200.4.200:16000] master.HMaster: > Failed to become active master > java.lang.IllegalStateException: The procedure WAL relies on the ability to > hsync for proper operation during component failures, but the underlying > filesystem does not support doing so. Please check the config value of > 'hbase.procedure.store.wal.use.hsync' to set the desired level of robustness > and ensure the config value of 'hbase.wal.dir' points to a FileSystem mount > that can provide it. > at > org.apache.hadoop.hbase.procedure2.store.wal.WALProcedureStore.rollWriter(WALProcedureStore.java:1036) > at > org.apache.hadoop.hbase.procedure2.store.wal.WALProcedureStore.recoverLease(WALProcedureStore.java:374) > at > org.apache.hadoop.hbase.procedure2.ProcedureExecutor.start(ProcedureExecutor.java:532) > at > org.apache.hadoop.hbase.master.HMaster.startProcedureExecutor(HMaster.java:1232) > at > org.apache.hadoop.hbase.master.HMaster.startServiceThreads(HMaster.java:1145) > at > org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(HMaster.java:837) > at > org.apache.hadoop.hbase.master.HMaster.startActiveMasterManager(HMaster.java:2026) > at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:547) > at java.lang.Thread.run(Thread.java:748) > {noformat} > The same configs is working in HBase-1.2.6 build properly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-20145) HMaster start fails with IllegalStateException when HADOOP_HOME is set
[ https://issues.apache.org/jira/browse/HBASE-20145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16437565#comment-16437565 ] Artem Ervits commented on HBASE-20145: -- I just got the same issue and can confirm that it's mixing jars on the classpath {code:java} /opt/hbase/hbase-2.0.0/lib/hadoop-annotations-2.7.4.jar:/opt/hbase/hbase-2.0.0/lib/hadoop-auth-2.7.4.jar:/opt/hbase/hbase-2.0.0/lib/hadoop-client-2.7.4.jar:/opt/hbase/hbase-2.0.0/lib/hadoop-common-2.7.4.jar:/opt/hbase/hbase-2.0.0/lib/hadoop-common-2.7.4-tests.jar:/opt/hbase/hbase-2.0.0/lib/hadoop-distcp-2.7.4.jar:/opt/hbase/hbase-2.0.0/lib/hadoop-hdfs-2.7.4.jar:/opt/hbase/hbase-2.0.0/lib/hadoop-hdfs-2.7.4-tests.jar:/opt/hbase/hbase-2.0.0/lib/hadoop-mapreduce-client-app-2.7.4.jar:/opt/hbase/hbase-2.0.0/lib/hadoop-mapreduce-client-common-2.7.4.jar:/opt/hbase/hbase-2.0.0/lib/hadoop-mapreduce-client-core-2.7.4.jar:/opt/hbase/hbase-2.0.0/lib/hadoop-mapreduce-client-hs-2.7.4.jar:/opt/hbase/hbase-2.0.0/lib/hadoop-mapreduce-client-jobclient-2.7.4.jar:/opt/hbase/hbase-2.0.0/lib/hadoop-mapreduce-client-shuffle-2.7.4.jar:/opt/hbase/hbase-2.0.0/lib/hadoop-minicluster-2.7.4.jar:/opt/hbase/hbase-2.0.0/lib/hadoop-yarn-api-2.7.4.jar:/opt/hbase/hbase-2.0.0/lib/hadoop-yarn-client-2.7.4.jar:/opt/hbase/hbase-2.0.0/lib/hadoop-yarn-common-2.7.4.jar{code} > HMaster start fails with IllegalStateException when HADOOP_HOME is set > -- > > Key: HBASE-20145 > URL: https://issues.apache.org/jira/browse/HBASE-20145 > Project: HBase > Issue Type: Bug > Environment: HBase-2.0-beta1. > Hadoop trunk version. > java version "1.8.0_144" >Reporter: Rohith Sharma K S >Assignee: Wei-Chiu Chuang >Priority: Critical > > It is observed that HMaster start is failed when HADOOP_HOME is set as env > while starting HMaster. HADOOP_HOME is pointing to Hadoop trunk version. > {noformat} > 2018-03-07 16:59:52,654 ERROR [master//10.200.4.200:16000] master.HMaster: > Failed to become active master > java.lang.IllegalStateException: The procedure WAL relies on the ability to > hsync for proper operation during component failures, but the underlying > filesystem does not support doing so. Please check the config value of > 'hbase.procedure.store.wal.use.hsync' to set the desired level of robustness > and ensure the config value of 'hbase.wal.dir' points to a FileSystem mount > that can provide it. > at > org.apache.hadoop.hbase.procedure2.store.wal.WALProcedureStore.rollWriter(WALProcedureStore.java:1036) > at > org.apache.hadoop.hbase.procedure2.store.wal.WALProcedureStore.recoverLease(WALProcedureStore.java:374) > at > org.apache.hadoop.hbase.procedure2.ProcedureExecutor.start(ProcedureExecutor.java:532) > at > org.apache.hadoop.hbase.master.HMaster.startProcedureExecutor(HMaster.java:1232) > at > org.apache.hadoop.hbase.master.HMaster.startServiceThreads(HMaster.java:1145) > at > org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(HMaster.java:837) > at > org.apache.hadoop.hbase.master.HMaster.startActiveMasterManager(HMaster.java:2026) > at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:547) > at java.lang.Thread.run(Thread.java:748) > {noformat} > The same configs is working in HBase-1.2.6 build properly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-20145) HMaster start fails with IllegalStateException when HADOOP_HOME is set
[ https://issues.apache.org/jira/browse/HBASE-20145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16437475#comment-16437475 ] Wei-Chiu Chuang commented on HBASE-20145: - Thanks [~rohithsharma] now I understand why: Turns out that if you point env HADOOP_HOME to a Hadoop3 path with hbase2.0 convenience binary, the classpath will contain both Hadoop 2.7.4 and Hadoop 3 jar files. Effectively causing class conflicts. Since Hadoop 3 jars are available, HBase is able to query StreamCapabilities of the output stream. However, because Hadoop 2.7.4 jars is loaded before Hadoop 3 jars in classpath, it loaded the HdfsDataOutputStream class implemented in Hadoop 2.7.4, which does not inherit from StreamCapabilities. {code:java} if (StreamCapabilities.CLASS.isAssignableFrom(stream.getClass())) { try { LOG.warn("stream type = " + stream.getWrappedStream().getClass().getCanonicalName()); result = ((Boolean)StreamCapabilities.METHOD.invoke(stream, capability)).booleanValue(); } catch (IllegalAccessException|IllegalArgumentException|InvocationTargetException exception) { LOG.warn("Your Hadoop installation's StreamCapabilities implementation doesn't match " + "our understanding of how it's supposed to work. Please file a JIRA and include " + "the following stack trace. In the mean time we're interpreting this behavior " + "difference as a lack of capability support, which will probably cause a failure.", exception); } } {code} This is not a problem in the code itself. But the code can be improved to log warning message when output stream class does not inherit from StreamCapabilities. > HMaster start fails with IllegalStateException when HADOOP_HOME is set > -- > > Key: HBASE-20145 > URL: https://issues.apache.org/jira/browse/HBASE-20145 > Project: HBase > Issue Type: Bug > Environment: HBase-2.0-beta1. > Hadoop trunk version. > java version "1.8.0_144" >Reporter: Rohith Sharma K S >Assignee: Wei-Chiu Chuang >Priority: Critical > > It is observed that HMaster start is failed when HADOOP_HOME is set as env > while starting HMaster. HADOOP_HOME is pointing to Hadoop trunk version. > {noformat} > 2018-03-07 16:59:52,654 ERROR [master//10.200.4.200:16000] master.HMaster: > Failed to become active master > java.lang.IllegalStateException: The procedure WAL relies on the ability to > hsync for proper operation during component failures, but the underlying > filesystem does not support doing so. Please check the config value of > 'hbase.procedure.store.wal.use.hsync' to set the desired level of robustness > and ensure the config value of 'hbase.wal.dir' points to a FileSystem mount > that can provide it. > at > org.apache.hadoop.hbase.procedure2.store.wal.WALProcedureStore.rollWriter(WALProcedureStore.java:1036) > at > org.apache.hadoop.hbase.procedure2.store.wal.WALProcedureStore.recoverLease(WALProcedureStore.java:374) > at > org.apache.hadoop.hbase.procedure2.ProcedureExecutor.start(ProcedureExecutor.java:532) > at > org.apache.hadoop.hbase.master.HMaster.startProcedureExecutor(HMaster.java:1232) > at > org.apache.hadoop.hbase.master.HMaster.startServiceThreads(HMaster.java:1145) > at > org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(HMaster.java:837) > at > org.apache.hadoop.hbase.master.HMaster.startActiveMasterManager(HMaster.java:2026) > at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:547) > at java.lang.Thread.run(Thread.java:748) > {noformat} > The same configs is working in HBase-1.2.6 build properly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-20145) HMaster start fails with IllegalStateException when HADOOP_HOME is set
[ https://issues.apache.org/jira/browse/HBASE-20145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16436668#comment-16436668 ] Rohith Sharma K S commented on HBASE-20145: --- Thanks [~jojochuang] for trying out. I have found the root cause for the failure. Did you build HBase-2.0.0-beta1 from source or directly used hbase*.tar.gz which is available in mirrors? Btw, I have answered in stack over flow question, see [hbase-error-illegalstateexception-when-starting-master-hsync|https://stackoverflow.com/questions/48709569/hbase-error-illegalstateexception-when-starting-master-hsync] . This should help > HMaster start fails with IllegalStateException when HADOOP_HOME is set > -- > > Key: HBASE-20145 > URL: https://issues.apache.org/jira/browse/HBASE-20145 > Project: HBase > Issue Type: Bug > Environment: HBase-2.0-beta1. > Hadoop trunk version. > java version "1.8.0_144" >Reporter: Rohith Sharma K S >Assignee: Wei-Chiu Chuang >Priority: Critical > > It is observed that HMaster start is failed when HADOOP_HOME is set as env > while starting HMaster. HADOOP_HOME is pointing to Hadoop trunk version. > {noformat} > 2018-03-07 16:59:52,654 ERROR [master//10.200.4.200:16000] master.HMaster: > Failed to become active master > java.lang.IllegalStateException: The procedure WAL relies on the ability to > hsync for proper operation during component failures, but the underlying > filesystem does not support doing so. Please check the config value of > 'hbase.procedure.store.wal.use.hsync' to set the desired level of robustness > and ensure the config value of 'hbase.wal.dir' points to a FileSystem mount > that can provide it. > at > org.apache.hadoop.hbase.procedure2.store.wal.WALProcedureStore.rollWriter(WALProcedureStore.java:1036) > at > org.apache.hadoop.hbase.procedure2.store.wal.WALProcedureStore.recoverLease(WALProcedureStore.java:374) > at > org.apache.hadoop.hbase.procedure2.ProcedureExecutor.start(ProcedureExecutor.java:532) > at > org.apache.hadoop.hbase.master.HMaster.startProcedureExecutor(HMaster.java:1232) > at > org.apache.hadoop.hbase.master.HMaster.startServiceThreads(HMaster.java:1145) > at > org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(HMaster.java:837) > at > org.apache.hadoop.hbase.master.HMaster.startActiveMasterManager(HMaster.java:2026) > at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:547) > at java.lang.Thread.run(Thread.java:748) > {noformat} > The same configs is working in HBase-1.2.6 build properly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-20145) HMaster start fails with IllegalStateException when HADOOP_HOME is set
[ https://issues.apache.org/jira/browse/HBASE-20145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16436326#comment-16436326 ] Wei-Chiu Chuang commented on HBASE-20145: - It doesn't seem to reproduce for me – tried hadoop trunk + hbase master, hadoop 3.0.0-beta1 + hbase 2.0.0-beta1. Neither reproduced. [~rohithsharma] could you share your hadoop and hbase configuration? I would actually think it makes sense to add additional check to see if the file system directory is erasure coded, and log extra message to avoid confusion. > HMaster start fails with IllegalStateException when HADOOP_HOME is set > -- > > Key: HBASE-20145 > URL: https://issues.apache.org/jira/browse/HBASE-20145 > Project: HBase > Issue Type: Bug > Environment: HBase-2.0-beta1. > Hadoop trunk version. > java version "1.8.0_144" >Reporter: Rohith Sharma K S >Assignee: Wei-Chiu Chuang >Priority: Critical > > It is observed that HMaster start is failed when HADOOP_HOME is set as env > while starting HMaster. HADOOP_HOME is pointing to Hadoop trunk version. > {noformat} > 2018-03-07 16:59:52,654 ERROR [master//10.200.4.200:16000] master.HMaster: > Failed to become active master > java.lang.IllegalStateException: The procedure WAL relies on the ability to > hsync for proper operation during component failures, but the underlying > filesystem does not support doing so. Please check the config value of > 'hbase.procedure.store.wal.use.hsync' to set the desired level of robustness > and ensure the config value of 'hbase.wal.dir' points to a FileSystem mount > that can provide it. > at > org.apache.hadoop.hbase.procedure2.store.wal.WALProcedureStore.rollWriter(WALProcedureStore.java:1036) > at > org.apache.hadoop.hbase.procedure2.store.wal.WALProcedureStore.recoverLease(WALProcedureStore.java:374) > at > org.apache.hadoop.hbase.procedure2.ProcedureExecutor.start(ProcedureExecutor.java:532) > at > org.apache.hadoop.hbase.master.HMaster.startProcedureExecutor(HMaster.java:1232) > at > org.apache.hadoop.hbase.master.HMaster.startServiceThreads(HMaster.java:1145) > at > org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(HMaster.java:837) > at > org.apache.hadoop.hbase.master.HMaster.startActiveMasterManager(HMaster.java:2026) > at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:547) > at java.lang.Thread.run(Thread.java:748) > {noformat} > The same configs is working in HBase-1.2.6 build properly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-20145) HMaster start fails with IllegalStateException when HADOOP_HOME is set
[ https://issues.apache.org/jira/browse/HBASE-20145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16435786#comment-16435786 ] Wei-Chiu Chuang commented on HBASE-20145: - Hi I'd like to work on it and see if the Hadoop trunk has a regression. Thanks. > HMaster start fails with IllegalStateException when HADOOP_HOME is set > -- > > Key: HBASE-20145 > URL: https://issues.apache.org/jira/browse/HBASE-20145 > Project: HBase > Issue Type: Bug > Environment: HBase-2.0-beta1. > Hadoop trunk version. > java version "1.8.0_144" >Reporter: Rohith Sharma K S >Priority: Critical > > It is observed that HMaster start is failed when HADOOP_HOME is set as env > while starting HMaster. HADOOP_HOME is pointing to Hadoop trunk version. > {noformat} > 2018-03-07 16:59:52,654 ERROR [master//10.200.4.200:16000] master.HMaster: > Failed to become active master > java.lang.IllegalStateException: The procedure WAL relies on the ability to > hsync for proper operation during component failures, but the underlying > filesystem does not support doing so. Please check the config value of > 'hbase.procedure.store.wal.use.hsync' to set the desired level of robustness > and ensure the config value of 'hbase.wal.dir' points to a FileSystem mount > that can provide it. > at > org.apache.hadoop.hbase.procedure2.store.wal.WALProcedureStore.rollWriter(WALProcedureStore.java:1036) > at > org.apache.hadoop.hbase.procedure2.store.wal.WALProcedureStore.recoverLease(WALProcedureStore.java:374) > at > org.apache.hadoop.hbase.procedure2.ProcedureExecutor.start(ProcedureExecutor.java:532) > at > org.apache.hadoop.hbase.master.HMaster.startProcedureExecutor(HMaster.java:1232) > at > org.apache.hadoop.hbase.master.HMaster.startServiceThreads(HMaster.java:1145) > at > org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(HMaster.java:837) > at > org.apache.hadoop.hbase.master.HMaster.startActiveMasterManager(HMaster.java:2026) > at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:547) > at java.lang.Thread.run(Thread.java:748) > {noformat} > The same configs is working in HBase-1.2.6 build properly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-20145) HMaster start fails with IllegalStateException when HADOOP_HOME is set
[ https://issues.apache.org/jira/browse/HBASE-20145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16389504#comment-16389504 ] Duo Zhang commented on HBASE-20145: --- The meaning for this exception is that, the FSDataOutputStream which is used for logging does not support hflush/hsync, which is not acceptable since calling hflush/hsync on the stream does not mean the data is persistent. This works for 1.2.6 just because we do not have the check in the code base of 1.2.6, but this can lead to data loss. This usually happens when if the file system is not HDFS, for example, S3FileSystem. And IIRC there is a issue for deploying HBase with EC enabled. For a OutputStream which supports EC then hflush/hsync will not work. And we haven't tested with hadoop trunk version yet. No sure what is the real problem. Thanks. > HMaster start fails with IllegalStateException when HADOOP_HOME is set > -- > > Key: HBASE-20145 > URL: https://issues.apache.org/jira/browse/HBASE-20145 > Project: HBase > Issue Type: Bug > Environment: HBase-2.0-beta1. > Hadoop trunk version. > java version "1.8.0_144" >Reporter: Rohith Sharma K S >Priority: Critical > > It is observed that HMaster start is failed when HADOOP_HOME is set as env > while starting HMaster. HADOOP_HOME is pointing to Hadoop trunk version. > {noformat} > 2018-03-07 16:59:52,654 ERROR [master//10.200.4.200:16000] master.HMaster: > Failed to become active master > java.lang.IllegalStateException: The procedure WAL relies on the ability to > hsync for proper operation during component failures, but the underlying > filesystem does not support doing so. Please check the config value of > 'hbase.procedure.store.wal.use.hsync' to set the desired level of robustness > and ensure the config value of 'hbase.wal.dir' points to a FileSystem mount > that can provide it. > at > org.apache.hadoop.hbase.procedure2.store.wal.WALProcedureStore.rollWriter(WALProcedureStore.java:1036) > at > org.apache.hadoop.hbase.procedure2.store.wal.WALProcedureStore.recoverLease(WALProcedureStore.java:374) > at > org.apache.hadoop.hbase.procedure2.ProcedureExecutor.start(ProcedureExecutor.java:532) > at > org.apache.hadoop.hbase.master.HMaster.startProcedureExecutor(HMaster.java:1232) > at > org.apache.hadoop.hbase.master.HMaster.startServiceThreads(HMaster.java:1145) > at > org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(HMaster.java:837) > at > org.apache.hadoop.hbase.master.HMaster.startActiveMasterManager(HMaster.java:2026) > at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:547) > at java.lang.Thread.run(Thread.java:748) > {noformat} > The same configs is working in HBase-1.2.6 build properly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-20145) HMaster start fails with IllegalStateException when HADOOP_HOME is set
[ https://issues.apache.org/jira/browse/HBASE-20145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16389491#comment-16389491 ] Rohith Sharma K S commented on HBASE-20145: --- I haven't explicitly set any configurations for Hadoop. Hadoop cluster is running with default configurations. For HBase, I have set basics configuration such as _hbase.rootdir_ _hbase.cluster.distributed_ and _hbase.zookeeper.quorum_ > HMaster start fails with IllegalStateException when HADOOP_HOME is set > -- > > Key: HBASE-20145 > URL: https://issues.apache.org/jira/browse/HBASE-20145 > Project: HBase > Issue Type: Bug > Environment: HBase-2.0-beta1. > Hadoop trunk version. > java version "1.8.0_144" >Reporter: Rohith Sharma K S >Priority: Critical > > It is observed that HMaster start is failed when HADOOP_HOME is set as env > while starting HMaster. HADOOP_HOME is pointing to Hadoop trunk version. > {noformat} > 2018-03-07 16:59:52,654 ERROR [master//10.200.4.200:16000] master.HMaster: > Failed to become active master > java.lang.IllegalStateException: The procedure WAL relies on the ability to > hsync for proper operation during component failures, but the underlying > filesystem does not support doing so. Please check the config value of > 'hbase.procedure.store.wal.use.hsync' to set the desired level of robustness > and ensure the config value of 'hbase.wal.dir' points to a FileSystem mount > that can provide it. > at > org.apache.hadoop.hbase.procedure2.store.wal.WALProcedureStore.rollWriter(WALProcedureStore.java:1036) > at > org.apache.hadoop.hbase.procedure2.store.wal.WALProcedureStore.recoverLease(WALProcedureStore.java:374) > at > org.apache.hadoop.hbase.procedure2.ProcedureExecutor.start(ProcedureExecutor.java:532) > at > org.apache.hadoop.hbase.master.HMaster.startProcedureExecutor(HMaster.java:1232) > at > org.apache.hadoop.hbase.master.HMaster.startServiceThreads(HMaster.java:1145) > at > org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(HMaster.java:837) > at > org.apache.hadoop.hbase.master.HMaster.startActiveMasterManager(HMaster.java:2026) > at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:547) > at java.lang.Thread.run(Thread.java:748) > {noformat} > The same configs is working in HBase-1.2.6 build properly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-20145) HMaster start fails with IllegalStateException when HADOOP_HOME is set
[ https://issues.apache.org/jira/browse/HBASE-20145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16389477#comment-16389477 ] Duo Zhang commented on HBASE-20145: --- Do you have ensure coding enabled on that directory? > HMaster start fails with IllegalStateException when HADOOP_HOME is set > -- > > Key: HBASE-20145 > URL: https://issues.apache.org/jira/browse/HBASE-20145 > Project: HBase > Issue Type: Bug > Environment: HBase-2.0-beta1. > Hadoop trunk version. > java version "1.8.0_144" >Reporter: Rohith Sharma K S >Priority: Critical > > It is observed that HMaster start is failed when HADOOP_HOME is set as env > while starting HMaster. HADOOP_HOME is pointing to Hadoop trunk version. > {noformat} > 2018-03-07 16:59:52,654 ERROR [master//10.200.4.200:16000] master.HMaster: > Failed to become active master > java.lang.IllegalStateException: The procedure WAL relies on the ability to > hsync for proper operation during component failures, but the underlying > filesystem does not support doing so. Please check the config value of > 'hbase.procedure.store.wal.use.hsync' to set the desired level of robustness > and ensure the config value of 'hbase.wal.dir' points to a FileSystem mount > that can provide it. > at > org.apache.hadoop.hbase.procedure2.store.wal.WALProcedureStore.rollWriter(WALProcedureStore.java:1036) > at > org.apache.hadoop.hbase.procedure2.store.wal.WALProcedureStore.recoverLease(WALProcedureStore.java:374) > at > org.apache.hadoop.hbase.procedure2.ProcedureExecutor.start(ProcedureExecutor.java:532) > at > org.apache.hadoop.hbase.master.HMaster.startProcedureExecutor(HMaster.java:1232) > at > org.apache.hadoop.hbase.master.HMaster.startServiceThreads(HMaster.java:1145) > at > org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(HMaster.java:837) > at > org.apache.hadoop.hbase.master.HMaster.startActiveMasterManager(HMaster.java:2026) > at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:547) > at java.lang.Thread.run(Thread.java:748) > {noformat} > The same configs is working in HBase-1.2.6 build properly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-20145) HMaster start fails with IllegalStateException when HADOOP_HOME is set
[ https://issues.apache.org/jira/browse/HBASE-20145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16389438#comment-16389438 ] Rohith Sharma K S commented on HBASE-20145: --- Here is the tail log trace {noformat} 2018-03-07 16:59:52,620 INFO [master//10.200.4.200:16000] wal.WALProcedureStore: Starting WAL Procedure Store lease recovery 2018-03-07 16:59:52,623 INFO [master//10.200.4.200:16000] util.FSHDFSUtils: Recover lease on dfs file hdfs://127.0.0.1:9000/hbase/MasterProcWALs/pv2-0001.log 2018-03-07 16:59:52,629 INFO [master//10.200.4.200:16000] util.FSHDFSUtils: Recovered lease, attempt=0 on file=hdfs://127.0.0.1:9000/hbase/MasterProcWALs/pv2-0001.log after 6ms 2018-03-07 16:59:52,630 WARN [master//10.200.4.200:16000] wal.WALProcedureStore: Remove uninitialized log: FileStatus{path=hdfs://127.0.0.1:9000/hbase/MasterProcWALs/pv2-0001.log; isDirectory=false; length=0; replication=3; blocksize=134217728; modification_time=1520422065550; access_time=1520422062450; owner=rsharmaks; group=supergroup; permission=rw-r--r--; isSymlink=false} 2018-03-07 16:59:52,630 INFO [master//10.200.4.200:16000] wal.ProcedureWALFile: Archiving hdfs://127.0.0.1:9000/hbase/MasterProcWALs/pv2-0001.log to hdfs://127.0.0.1:9000/hbase/oldWALs/pv2-0001.log 2018-03-07 16:59:52,654 ERROR [master//10.200.4.200:16000] master.HMaster: Failed to become active master java.lang.IllegalStateException: The procedure WAL relies on the ability to hsync for proper operation during component failures, but the underlying filesystem does not support doing so. Please check the config value of 'hbase.procedure.store.wal.use.hsync' to set the desired level of robustness and ensure the config value of 'hbase.wal.dir' points to a FileSystem mount that can provide it. at org.apache.hadoop.hbase.procedure2.store.wal.WALProcedureStore.rollWriter(WALProcedureStore.java:1036) at org.apache.hadoop.hbase.procedure2.store.wal.WALProcedureStore.recoverLease(WALProcedureStore.java:374) at org.apache.hadoop.hbase.procedure2.ProcedureExecutor.start(ProcedureExecutor.java:532) at org.apache.hadoop.hbase.master.HMaster.startProcedureExecutor(HMaster.java:1232) at org.apache.hadoop.hbase.master.HMaster.startServiceThreads(HMaster.java:1145) at org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(HMaster.java:837) at org.apache.hadoop.hbase.master.HMaster.startActiveMasterManager(HMaster.java:2026) at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:547) at java.lang.Thread.run(Thread.java:748) 2018-03-07 16:59:52,655 ERROR [master//10.200.4.200:16000] master.HMaster: Master server abort: loaded coprocessors are: [] 2018-03-07 16:59:52,655 ERROR [master//10.200.4.200:16000] master.HMaster: Unhandled exception. Starting shutdown. java.lang.IllegalStateException: The procedure WAL relies on the ability to hsync for proper operation during component failures, but the underlying filesystem does not support doing so. Please check the config value of 'hbase.procedure.store.wal.use.hsync' to set the desired level of robustness and ensure the config value of 'hbase.wal.dir' points to a FileSystem mount that can provide it. at org.apache.hadoop.hbase.procedure2.store.wal.WALProcedureStore.rollWriter(WALProcedureStore.java:1036) at org.apache.hadoop.hbase.procedure2.store.wal.WALProcedureStore.recoverLease(WALProcedureStore.java:374) at org.apache.hadoop.hbase.procedure2.ProcedureExecutor.start(ProcedureExecutor.java:532) at org.apache.hadoop.hbase.master.HMaster.startProcedureExecutor(HMaster.java:1232) at org.apache.hadoop.hbase.master.HMaster.startServiceThreads(HMaster.java:1145) at org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(HMaster.java:837) at org.apache.hadoop.hbase.master.HMaster.startActiveMasterManager(HMaster.java:2026) at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:547) at java.lang.Thread.run(Thread.java:748) {noformat} > HMaster start fails with IllegalStateException when HADOOP_HOME is set > -- > > Key: HBASE-20145 > URL: https://issues.apache.org/jira/browse/HBASE-20145 > Project: HBase > Issue Type: Bug > Environment: HBase-2.0-beta1. > Hadoop trunk version. > java version "1.8.0_144" >Reporter: Rohith Sharma K S >Priority: Critical > > It is observed that HMaster start is failed when HADOOP_HOME is set as env > while starting HMaster. HADOOP_HOME is pointing to Hadoop trunk version. > {noformat} > 2018-03-07 16:59:52,654 ERROR [master//10.200.4.200:16000] master.HMaster: > Failed to become active master >