[
https://issues.apache.org/jira/browse/AMBARI-24172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Watson updated AMBARI-24172:
------------------------------------
Description:
Knox uses an access key to auth the traffic to Hive. When Hive is restarted,
the access key that Knox uses changes as well, but Knox won't pickup the new
access key until it is also restarted.
In short, Knox needs to be restarted if Hive is restarted and the stack
advisor does not alert you to this fact. Instead, you encounter "HTTP 500"
errors when accessing Hive until Knox is restarted.
was:
Knox uses an access key to auth the traffic to Hive. When Hive is restarted,
the access key that Knox uses changes as well, but Knox won't pickup the new
access key until it is also restarted.
In short, Knox needs to be restarted if Hive is restarted and the stack advisor
does not alert you to this fact. Instead, you encounter 500 errors when
accessing Hive until Knox is restarted.
> Stack Advisor Does Not Alert Knox Restart Needed After Hive Restart
> -------------------------------------------------------------------
>
> Key: AMBARI-24172
> URL: https://issues.apache.org/jira/browse/AMBARI-24172
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.6.2
> Reporter: William Watson
> Priority: Major
>
> Knox uses an access key to auth the traffic to Hive. When Hive is restarted,
> the access key that Knox uses changes as well, but Knox won't pickup the new
> access key until it is also restarted.
> In short, Knox needs to be restarted if Hive is restarted and the stack
> advisor does not alert you to this fact. Instead, you encounter "HTTP 500"
> errors when accessing Hive until Knox is restarted.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
