[
https://issues.apache.org/jira/browse/HBASE-6698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13459730#comment-13459730
]
ramkrishna.s.vasudevan commented on HBASE-6698:
-----------------------------------------------
As per my analysis, before the HBaseRPCServer on the RS could start and set the
volatile variable 'started' the master started the assignment because the RS
registration got completed successfully.
{code}
Caused by: org.apache.hadoop.ipc.RemoteException:
org.apache.hadoop.hbase.ipc.ServerNotRunningYetException: Server is not running
yet
at
org.apache.hadoop.hbase.ipc.HBaseServer$Handler.run(HBaseServer.java:1798)
at org.apache.hadoop.hbase.ipc.HBaseClient.call(HBaseClient.java:1300)
at
org.apache.hadoop.hbase.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:178)
... 11 more
{code}
This shows that the assignment failed due to Servernotrunningexcep.
Connected to master logs comes even before this
{code}
2012-09-20 13:10:31,810 INFO
[RegionServer:0;asf011.sp2.ygridcore.net,34620,1348146629931]
regionserver.HRegionServer(1943): Attempting connect to Master server at
asf011.sp2.ygridcore.net,49804,1348146629519
2012-09-20 13:10:31,841 INFO
[RegionServer:0;asf011.sp2.ygridcore.net,34620,1348146629931]
regionserver.HRegionServer(1952): Connected to master at
asf011.sp2.ygridcore.net/67.195.138.20:49804
2012-09-20 13:10:31,841 INFO
[RegionServer:0;asf011.sp2.ygridcore.net,34620,1348146629931]
regionserver.HRegionServer(1998): Telling master at
asf011.sp2.ygridcore.net,49804,1348146629519 that we are up with port=34620,
startcode=1348146629931
2012-09-20 13:10:31,882 INFO [IPC Server handler 0 on 49804]
master.ServerManager(307): Registering
server=asf011.sp2.ygridcore.net,34620,1348146629931
2012-09-20 13:10:31,893 DEBUG
[RegionServer:0;asf011.sp2.ygridcore.net,34620,1348146629931]
regionserver.HRegionServer(1171): Config from master:
hbase.rootdir=hdfs://localhost:52552/user/jenkins/hbase
2012-09-20 13:10:31,894 DEBUG
[RegionServer:0;asf011.sp2.ygridcore.net,34620,1348146629931]
regionserver.HRegionServer(1171): Config from master:
fs.default.name=hdfs://localhost:52552
2012-09-20 13:10:31,894 INFO
[RegionServer:0;asf011.sp2.ygridcore.net,34620,1348146629931]
regionserver.HRegionServer(1164): Master passed us hostname to use.
Was=asf011.sp2.ygridcore.net, Now=asf011.sp2.ygridcore.net
{code}
And the ROOT assignment also started
{code}
012-09-20 13:10:33,811 INFO
[Master:0;asf011.sp2.ygridcore.net,49804,1348146629519]
master.AssignmentManager(1579): Assigning region -ROOT-,,0.70236052 to
asf011.sp2.ygridcore.net,34620,1348146629931
2012-09-20 13:10:33,811 INFO
[Master:0;asf011.sp2.ygridcore.net,49804,1348146629519]
master.RegionStates(250): Region {NAME => '-ROOT-,,0', STARTKEY => '', ENDKEY
=> '', ENCODED => 70236052,} transitioned from {-ROOT-,,0.70236052
state=OFFLINE, ts=1348146633581, server=null} to {-ROOT-,,0.70236052
state=PENDING_OPEN, ts=1348146633811,
server=asf011.sp2.ygridcore.net,34620,1348146629931}
{code}
I think this should be addressed in a seperate JIRA. Let me know if i can
commit the patch?
> Refactor checkAndPut and checkAndDelete to use doMiniBatchMutation
> ------------------------------------------------------------------
>
> Key: HBASE-6698
> URL: https://issues.apache.org/jira/browse/HBASE-6698
> Project: HBase
> Issue Type: Improvement
> Reporter: ramkrishna.s.vasudevan
> Fix For: 0.96.0
>
> Attachments: HBASE-6698_1.patch, HBASE-6698_2.patch,
> HBASE-6698_3.patch, HBASE-6698_5.patch, HBASE-6698_6.patch,
> HBASE-6698_6.patch, HBASE-6698_6.patch, HBASE-6698_6.patch,
> HBASE-6698_7.patch, HBASE-6698_8.patch, HBASE-6698_8.patch, HBASE-6698.patch
>
>
> Currently the checkAndPut and checkAndDelete api internally calls the
> internalPut and internalDelete. May be we can just call doMiniBatchMutation
> only. This will help in future like if we have some hooks and the CP
> handles certain cases in the doMiniBatchMutation the same can be done while
> doing a put thro checkAndPut or while doing a delete thro checkAndDelete.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
