RE: problem in launching HBase

I'm so sorry that I make a mistake. The Hadoop configuration files are attached in the previous e-mail. The hbase-site.xml are attached, pls check it. -Original Message- From: Ted Yu [mailto:yuzhih...@gmail.com] Sent: Tuesday, November 15, 2016 1:25 PM To: user@hbase.apache.org

Re: problem in launching HBase

I don't see hbase-site.xml attached. Consider using pastebin. On Mon, Nov 14, 2016 at 9:19 PM, QI Congyun wrote: > > The name node and data node are running normally, such as the following > process. The file "hbase-site.xml" and other associated files are

RE: problem in launching HBase

The name node and data node are running normally, such as the following process. The file "hbase-site.xml" and other associated files are enclosed. Thanks. ---

Re: problem in launching HBase

2016-10-31 15:49:57,528 FATAL [localhost:16000.activeMasterManager] master.HMaster: Failed to become active master java.net.ConnectException: Call From hadoop2/127.0.0.1 to localhost:8020 failed on connection exception: java.net.ConnectException: Connection refused; For more details see:

RE: problem in launching HBase

Dear Ted, I had learn the HBase quick-start cookbook although I have not yet read all of the document, I have known how to configure the HBase primary parameters and basic operation. I had ever tried to both make HBase control to use zookeeper and cancel HBase to start zookeeper server via

problem in launching HBase

2016-11-10 11:25:14,177 INFO [main-SendThread(localhost:2181)] zookeeper.ClientCnxn: Opening socket connection to server localhost/ *127.0.0.1*:2181. Will not attempt to authenticate using SASL (unknown error) Was the zookeeper quorum running on the localhost ? In the future, use

RE: "Quickstart" on OmniOS/illumos not working, java eats CPU

Dear Ted, I'm a beginner about Hadoop and Hbase, perhaps a potential or primary errors are made out, sorry to give you a trouble. -Original Message- From: QI Congyun Sent: Tuesday, November 15, 2016 10:26 AM To: 'Ted Yu'; user@hbase.apache.org Subject: RE: "Quickstart" on

RE: "Quickstart" on OmniOS/illumos not working, java eats CPU

My previous e-mail is attached, pls check if the relative traces are enough to investigate or not? My node configuration are also enclosed. Thanks a lot. -Original Message- From: Ted Yu [mailto:yuzhih...@gmail.com] Sent: Tuesday, November 15, 2016 10:16 AM To: user@hbase.apache.org

Re: "Quickstart" on OmniOS/illumos not working, java eats CPU

Congyun: I searched my Inbox but didn't see your previous post. Did you post to user@hbase ? Since your issue was likely different from what Olaf experienced, mind starting another thread ? Cheers On Mon, Nov 14, 2016 at 6:07 PM, QI Congyun wrote: > Dear

RE: "Quickstart" on OmniOS/illumos not working, java eats CPU

Dear Olaf, I have some problems when I try to install and launch the Hbase, I try to send a request e-mail to the relative e-mail box, but no one reply with me, are you kindly enough to tell me who give some reasonable technical support for HBase? Thanks so much. -Original Message-

Re: Verification of Short Circuit Reads

Thanks for taking a look Josh. It appears the HDFS client process must have execute permissions on that directory, presumably it's depending on a listing operation. Adding o+x to the base directory of dfs.domain.socket.path, in my case, /var/run/hadoop-hdfs, seems to have resolved the issue. At

Re: "Quickstart" on OmniOS/illumos not working, java eats CPU

Hi, I will think about it, but both the OpenJDK1.7 by OmniTI and the Oracle JDK1.8 set the value to 256. In case of problems I will check it again. Olaf On 14/11/2016 19:08, Esteban Gutierrez wrote: Just a quick observation here: the number of max file descriptors configured is way too low

Re: "Quickstart" on OmniOS/illumos not working, java eats CPU

Problem disappeared. I haven't done any particular test, but no more CPU at 100%. Here the 2 logs and 2 stack traces. http://pastebin.com/FVWP56b6 http://pastebin.com/gXnnwriw http://pastebin.com/GFhmg4nu http://pastebin.com/QdreZLXF I also tried to use stack from jdk1.8 to get a stack trace

Re: "Quickstart" on OmniOS/illumos not working, java eats CPU

Just a quick observation here: the number of max file descriptors configured is way too low in my opinion. Also, it has been few years since last time I played with OpenSolaris but I'm going to assume that Illumos you could run truss and the prstat commands and trace the jvm to see whats going on.

Re: "Quickstart" on OmniOS/illumos not working, java eats CPU

Olaf: After switching away from OmniOS Java, did you still encounter similar problem ? If so, mind updating the thread with log / stack trace ? Thanks On Sun, Nov 13, 2016 at 8:40 AM, Olaf Marzocchi wrote: > I checked and they are located in the same folder. > I found