[ 
https://issues.apache.org/jira/browse/HBASE-20324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16436435#comment-16436435
 ] 

stack commented on HBASE-20324:
-------------------------------

It works for me in an environment here....

I see this in your logs:

2018-03-31 05:00:22,190 INFO  [master/abhishekk1:16000] master.ServerManager: 
Waiting on regionserver count=2; waited=4466ms, expecting min=1 server(s), 
max=NO_LIMIT server(s), timeout=4500ms, lastChange=-1502ms
2018-03-31 05:00:22,241 INFO  [master/abhishekk1:16000] master.ServerManager: 
Finished waiting on RegionServer count=2; waited=4516ms, expected min=1 
server(s), max=NO_LIMIT server(s), master is running
2018-03-31 05:00:22,241 INFO  [master/abhishekk1:16000] master.ServerManager: 
Server serverName=abhishekk2.pne.ven.veritas.com,16020,1522040698709 rejected; 
we already have abhishekk2.pne.ven.veritas.com,16020,1522486814482 registered 
with same hostname and port
2018-03-31 05:00:22,241 INFO  [master/abhishekk1:16000] master.ServerManager: 
Server serverName=abhishekk2.pne.ven.veritas.com,16020,1522041869374 rejected; 
we already have abhishekk2.pne.ven.veritas.com,16020,1522486814482 registered 
with same hostname and port
2018-03-31 05:00:22,241 INFO  [master/abhishekk1:16000] master.ServerManager: 
Server serverName=abhishekk2.pne.ven.veritas.com,16020,1522051522575 rejected; 
we already have abhishekk2.pne.ven.veritas.com,16020,1522486814482 registered 
with same hostname and port
2018-03-31 05:00:22,241 INFO  [master/abhishekk1:16000] master.ServerManager: 
Server serverName=abhishekk2.pne.ven.veritas.com,16020,1522063726382 rejected; 
we already have abhishekk2.pne.ven.veritas.com,16020,1522486814482 registered 
with same hostname and port
2018-03-31 05:00:22,241 INFO  [master/abhishekk1:16000] master.ServerManager: 
Server serverName=abhishekk2.pne.ven.veritas.com,16020,1522417574534 rejected; 
we already have abhishekk2.pne.ven.veritas.com,16020,1522486814482 registered 
with same hostname and port
2018-03-31 05:00:22,241 INFO  [master/abhishekk1:16000] master.ServerManager: 
Server serverName=abhishekk2.pne.ven.veritas.com,16020,1522480363659 rejected; 
we already have abhishekk2.pne.ven.veritas.com,16020,1522486814482 registered 
with same hostname and port
2018-03-31 05:00:22,242 INFO  [master/abhishekk1:16000] master.ServerManager: 
Server serverName=abhishekk3.pne.ven.veritas.com,16020,1522040703686 rejected; 
we already have abhishekk3.pne.ven.veritas.com,16020,1522486816915 registered 
with same hostname and port
2018-03-31 05:00:22,242 INFO  [master/abhishekk1:16000] master.ServerManager: 
Server serverName=abhishekk3.pne.ven.veritas.com,16020,1522041871247 rejected; 
we already have abhishekk3.pne.ven.veritas.com,16020,1522486816915 registered 
with same hostname and port
2018-03-31 05:00:22,242 INFO  [master/abhishekk1:16000] master.ServerManager: 
Server serverName=abhishekk3.pne.ven.veritas.com,16020,1522051524387 rejected; 
we already have abhishekk3.pne.ven.veritas.com,16020,1522486816915 registered 
with same hostname and port
2018-03-31 05:00:22,242 INFO  [master/abhishekk1:16000] master.ServerManager: 
Server serverName=abhishekk3.pne.ven.veritas.com,16020,1522063727826 rejected; 
we already have abhishekk3.pne.ven.veritas.com,16020,1522486816915 registered 
with same hostname and port
2018-03-31 05:00:22,242 INFO  [master/abhishekk1:16000] master.ServerManager: 
Server serverName=abhishekk3.pne.ven.veritas.com,16020,1522417575830 rejected; 
we already have abhishekk3.pne.ven.veritas.com,16020,1522486816915 registered 
with same hostname and port
2018-03-31 05:00:22,242 INFO  [master/abhishekk1:16000] master.ServerManager: 
Server serverName=abhishekk3.pne.ven.veritas.com,16020,1522480363633 rejected; 
we already have abhishekk3.pne.ven.veritas.com,16020,1522486816915 registered 
with same hostname and port
....

Is there an issue w/ naming in your cluster? abhishekk3.pne.ven.veritas.com is 
where your Master is running so interesting there are these complaints coming 
in.

Root complaint seems to be this:

SaslException): GSS initiate failed

... which reading around can have myriad causes with naming being one of them.

I'm not expert in setting up these environments. See if you can provide more 
info on your context. Thanks.



> Hbase master fails to become active in kerberos environment
> -----------------------------------------------------------
>
>                 Key: HBASE-20324
>                 URL: https://issues.apache.org/jira/browse/HBASE-20324
>             Project: HBase
>          Issue Type: Bug
>         Environment: Hbase 2.0.0-beta2
> zookeeper-3.5.3-beta
> 3 nodes Env
> Kdc server on namenode
> *hadoop-2.7.3*
> *--Configured with keytabs(abhishekk1/2/3 are nodes)* 
>    *abhishekk1 is namenode/hmaster*
>    *abhishekk2/3 are datanodes/regionservers*
>            Reporter: Abhishek Kulkarni
>            Priority: Blocker
>             Fix For: 2.0.0
>
>         Attachments: hbase-root-master-.log, hbase-root-regionserver.log
>
>
>  
> [^hbase-root-master-.log]
> ^[^hbase-root-regionserver.log]^
>  
> ^^Trying to resolve this form last one month with different forums but not 
> able to resovleat all.^^



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to