Sounds good! I'll do that change.
Thx,
J-D
On Tue, Mar 29, 2011 at 4:01 PM, Jeff Whiting wrote:
> I'm not sure...the key to everything was realizing picking up on
> RemoteException in "Unable to replicate because
> org.apache.hadoop.ipc.RemoteException" and realizing that it was on the
> replic
I'm not sure...the key to everything was realizing picking up on RemoteException in "Unable to
replicate because org.apache.hadoop.ipc.RemoteException" and realizing that it was on the
replication cluster.
If it said something like "Unable to replicate. Destination cluster threw an exception:
Do you think the issue could be better reported to the user?
I find the error message obvious, but I've been around that code for a
year now :)
Thx!
J-D
On Tue, Mar 29, 2011 at 9:21 AM, Jeff Whiting wrote:
> That was it. I didn't realize that was the exception on the remote
> cluster...make s
That was it. I didn't realize that was the exception on the remote
cluster...make sense now.
~Jeff
On 3/28/2011 3:34 PM, Jean-Daniel Cryans wrote:
The slave cluster is saying that the table user-session doesn't
exist... is it the case?
J-D
On Mon, Mar 28, 2011 at 1:38 PM, Jeff Whiting wrot
The slave cluster is saying that the table user-session doesn't
exist... is it the case?
J-D
On Mon, Mar 28, 2011 at 1:38 PM, Jeff Whiting wrote:
> My regions weren't very well balanced so I ran the "balancer" in hbase shell
> and my region servers starting getting a whole bunch of exceptions li
My regions weren't very well balanced so I ran the "balancer" in hbase shell and my region servers
starting getting a whole bunch of exceptions like:
2011-03-28 14:33:27,402 DEBUG org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler: Opened
response-index,,1300386337049.70eded10f984a3
