You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Wei-Chiu Chuang (Jira)" <ji...@apache.org> on 2021/06/15 04:21:00 UTC
[jira] [Comment Edited] (HBASE-26007) java.io.IOException: Invalid
token in javax.security.sasl.qop: ^DDI
[ https://issues.apache.org/jira/browse/HBASE-26007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17363369#comment-17363369 ]
Wei-Chiu Chuang edited comment on HBASE-26007 at 6/15/21, 4:20 AM:
-------------------------------------------------------------------
You probably had an invalid configuration value in hdfs-site.xml.
Because there's no full stack trace, it's hard to know exactly which config is wrong, but try search "^DDI" in your config file.
Possible config keys:
dfs.encrypt.data.overwrite.downstream.new.qop
ingress.port.sasl.prop.<port>
was (Author: jojochuang):
You probably had an invalid configuration value in hdfs-site.xml.
Because there's no full stack trace, it's hard to know exactly which config is wrong, but try search "^DDI" in your config file.
dfs.encrypt.data.overwrite.downstream.new.qop
> java.io.IOException: Invalid token in javax.security.sasl.qop: ^DDI
> -------------------------------------------------------------------
>
> Key: HBASE-26007
> URL: https://issues.apache.org/jira/browse/HBASE-26007
> Project: HBase
> Issue Type: Bug
> Components: master
> Affects Versions: 2.3.5
> Reporter: Venkat A
> Priority: Blocker
>
> Hi All,
> We have Hadoop 3.2.2 and HBase 2.3.5 Versions installed. (java version "1.8.0_291")
>
> While bringing up HBase master, I'm seeing following error messages in HBase master log.
>
> Other HDFS. clients like Spark,MapReduce,Solr etc are able to write HDFS but HBase is unable to write its meta files in HDFS with following exceptions.
>
> > Summary of Error logs from hbase master
> 2021-06-15 03:57:45,968 INFO [Thread-7] hdfs.DataStreamer: Exception in createBlockOutputStream
> java.io.IOException: Invalid token in javax.security.sasl.qop: ^DD
> 2021-06-15 03:57:45,939 WARN [Thread-7] hdfs.DataStreamer: Abandoning BP-1583998547-10.10.10.3-1622148262434:blk_1073743393_2570
> 2021-06-15 03:57:45,946 WARN [Thread-7] hdfs.DataStreamer: Excluding datanode DatanodeInfoWithStorage[10.10.10.3:50010,DS-281c3377-2bc1-47ea-8302-43108ee69430,DISK]
> 2021-06-15 03:57:45,994 WARN [Thread-7] hdfs.DataStreamer: DataStreamer Exception
> org.apache.hadoop.ipc.RemoteException(java.io.IOException): File /hbase/data/data/hbase/meta/.tmp/.tableinfo.0000000001 could only be written to 0 of the 1 minReplication nodes. There are 3 datanode(s) running and 3 node(s) are excluded in this operation.
> 2021-06-15 03:57:46,023 INFO [Thread-9] hdfs.DataStreamer: Exception in createBlockOutputStream
> java.io.IOException: Invalid token in javax.security.sasl.qop: ^DDI
> 2021-06-15 03:57:46,035 INFO [Thread-9] hdfs.DataStreamer: Exception in createBlockOutputStream
> java.io.IOException: Invalid token in javax.security.sasl.qop: ^DD
> 2021-06-15 03:57:46,508 ERROR [main] regionserver.HRegionServer: Failed construction RegionServer
> java.io.IOException: Failed update hbase:meta table descriptor
> 2021-06-15 03:57:46,509 ERROR [main] master.HMasterCommandLine: Master exiting
> java.lang.RuntimeException: Failed construction of Master: class org.apache.hadoop.hbase.master.HMaster.
> Caused by: java.io.IOException: Failed update hbase:meta table descriptor
>
> Not sure what is the root cause behind this. Any comments/suggestions on this is much appreciated.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)