[jira] [Commented] (AMBARI-13228) HBase service start fails after manual stack upgrade with missing PhoenixRpcSchedulerFactory class error

["Anu Ramani (JIRA)" <ji...@apache.org>]

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

Anu Ramani commented on AMBARI-13228:
-------------------------------------

1. This issue still seems to occur in Ambari 2.1.2 when we enable Phoenix service through HBase. 
2. This is an on a clean-install of HDP 2.3.2 and ambari-server-2.1.2-374.x86_64.rpm
3. When I verified the changes for this commit on our 'ambari-server-2.1.2-374' version, I noticed that the following snippet of code was missing in upgradeHelper.py

{code}
def check_phoenix_component_existence():
  try:
    resultset = curl(Options.COMPONENTS_FORMAT.format(Options.PHOENIX_QUERY_SERVER), validate=False, parse=True)
  except HTTPError as e:
    raise TemplateProcessingException(str(e))
  if "ServiceComponentInfo" in resultset and "total_count" in resultset["ServiceComponentInfo"]:
    try:
      component_count = int(resultset["ServiceComponentInfo"]["total_count"])
      if component_count > 0:
        return True
    except ValueError:
      return False
  return False
{code}

4. Should there be any modifications done on clean-install and enabling Phoenix on HBase?

> HBase service start fails after manual stack upgrade with missing PhoenixRpcSchedulerFactory class error
> --------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-13228
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13228
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Andrew Onischuk
>            Assignee: Andrew Onischuk
>             Fix For: 2.1.2
>
>
>  PhoenixRpcSchedulerFactory class  exist in the property hbase.region.server.rpc.scheduler.factory.class even without installed Phoenix



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)