Roshan aby created HBASE-28062:
----------------------------------

             Summary: An exception was thrown by 
org.apache.hadoop.hbase.io.asyncfs.FanOutBlockAsyncDFSOutputHelper$4.operationComplete()
                 Key: HBASE-28062
                 URL: https://issues.apache.org/jira/browse/HBASE-28062
             Project: HBase
          Issue Type: Bug
          Components: master
    Affects Versions: 2.4.17
         Environment: Hbase version - 2.4.17 (not built by me, it was prebuilt 
by apache)

Hadoop version - 3.3.1 (not built by me, it was prebuilt by apache)

Zookeeper version - 3.8.2 (not built by me, it was prebuilt by apache)

OS - Ubuntu 20.04 x86_64

Java Version - 8
            Reporter: Roshan aby
         Attachments: hbase-env.sh, hbase-site.xml

When I try running hbase using the code *./start-hbase.sh* , the terminal 
doesn't show an error or failure but logs do show it. Here I am dropping the 
link to the entire log file [log 
file|[http://justpaste.it/aqyjh|https://justpaste.it/aqyjh]] . I have tried 
some forums and reading documentation but nothing helped. Hadoop is compatible 
with Hbase version asHbase created a folder in Hadoop named */hbase* in the 
root directory of Hadoop and the directory does contain couple of directories 
(.hbck, .tmp, MasterData, WALs, archive, etc) and 2 files (hbase.id, 
hbase.version). So I don't think compatibility between Hadoop and Hbase is the 
issue here. Everything is running locally, literally everything as I am just 
testing some stuff. Also when I try doing *bin/hbase shell* , then the shell 
starts but anything I do in the shell for example if I type {*}status{*}, in 
the shell, I get the error which is same if I type any other code as "Error: 
KeeperErrorCode = ConnectionLoss for /hbase/master". I have uploaded two files 
of hbase which are the only two files I have altered to from the pre-built 
version of Apache. If you need any more information, please let me know.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to