RE: Fully distributed mode on Windows

2016-08-15 Thread Xiaochun Liang
Hi Dan, Very appreciated with the sharing! Regards, xiaochun -Original Message- From: Daniel Vimont [mailto:dan...@commonvox.org] Sent: Tuesday, August 16, 2016 10:50 AM To: user@hbase.apache.org Subject: Re: Fully distributed mode on Windows Hello Xiaochun, Below are the notes that

Re: (BUG)ShortCircuitLocalReads Failed when enabled replication

2016-08-15 Thread yangming860101
online cluster configuration: hdfs-site.xml hbase-site.xml -- View this message in context: http://apache-hbase.679495.n3.nabble.com/BUG-ShortCircui

Re: (BUG)ShortCircuitLocalReads Failed when enabled replication

2016-08-15 Thread yangming860101
online cluster configuration: hdfs-site.xml hbase-site.xml -- View this message in context: http://apache-hbase.679495.n3.nabble.com/BUG-ShortCircui

Re: (BUG)ShortCircuitLocalReads Failed when enabled replication

2016-08-15 Thread yangming860101
/*Are you seeing it for all the log files? The local ReplicationSource will handle the WALs for replication from this RS. But it may so happen that this RS went down and so another took charge of doing replication of the WAL files originated at the current down RS. Those WALs might not be local for

Re: (BUG)ShortCircuitLocalReads Failed when enabled replication

2016-08-15 Thread yangming860101
HBase log: 2016-08-12 14:25:56,738 DEBUG org.apache.hadoop.hbase.replication.regionserver.ReplicationSource: Opening log for replication dn7%2C60020%2C1470216726863.1470983077165 at 28175754 2016-08-12 14:25:56,740 WARN org.apache.hadoop.hdfs.DFSClient: BlockReaderLocal requested with incorrect of

Re: (BUG)ShortCircuitLocalReads Failed when enabled replication

2016-08-15 Thread yangming860101
dfs.domain.socket.path not configured.There is no similar fail when ShortCircuitLocalReads ,just only for log files(replication). hdfs verion:1.2.1 dfs.block.local-path-access.user hadoop dfs.client.read.shortcircuit true hbase version:0.94.20 dfs.client.read.shortcircuit

Re: Fully distributed mode on Windows

2016-08-15 Thread Daniel Vimont
Hello Xiaochun, Below are the notes that I took when I was trying to install HBase in a Windows environment using Cygwin. These notes are from approximately May of 2015, so I have no idea how well they apply to any current attempt to install HBase in this kind of environment. Also, I'm afraid that

RE: Fully distributed mode on Windows

2016-08-15 Thread Xiaochun Liang
Thanks Dan! Looks like it is a little bit harder to setup HBase on Windows with Cygwin. Thanks a lot for your suggestions. Looks like I still need to setup HBase with Cygwin. Could you please share the problems you met? Regards, xiaochun -Original Message- From: Daniel Vimont [mailto:

Re: distcp hbase-0.94.6(CDH4.5) hfiles to hbase1.2(CDH5.8)?

2016-08-15 Thread Ted Yu
Please verify that your 0.94 cluster is configured with hfile v2. Config hfile.format.version should have value of 2. To obtain region boundaries, you can use 'describe' hbase shell command. Cheers On Mon, Aug 15, 2016 at 9:48 AM, Rob Verkuylen wrote: > The 2nd cluster is an operational cluste

Re: distcp hbase-0.94.6(CDH4.5) hfiles to hbase1.2(CDH5.8)?

2016-08-15 Thread Rob Verkuylen
The 2nd cluster is an operational cluster, so option 2 seems to fit nicely. Will the LoadIncrementalHFiles on the Hbase1.2 cluster be able to process the 0.94 version Hfiles? Also is there a convenient way to get the region splits from the old hfiles, or is going though them the only option? On

Re: distcp hbase-0.94.6(CDH4.5) hfiles to hbase1.2(CDH5.8)?

2016-08-15 Thread Stack
On Sun, Aug 14, 2016 at 12:09 AM, Rob Verkuylen wrote: > We're recovering from a crash of hbase-0.94.6 where the master refuses to > come up, while hdfs is fine. Why this happened exactly is something we're > looking into. > > What does the log say? St.Ack > In the meantime we're looking to mi

responseTooSlow warnings and hdfs ConnectTimeoutExceptions

2016-08-15 Thread LeBlanc, Jacob
Hi all, We have a production cluster where we are seeing periodic client RPC timeouts as well as responseTooSlow warnings, scanner lease expirations, and hdfs read timeouts on some regions servers. We've been trying to diagnose this for a couple weeks, but still no luck on finding a root cause.