[
https://issues.apache.org/jira/browse/KNOX-2656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joathan Levenson updated KNOX-2656:
-----------------------------------
Description:
When configuring Knox to use the HA provider with sticky sessions and
loadbalancing enabled for Hive, using an ODBC driver to connect causes the
following error:
{code:java}
SQL Error [35] [S1000]: [Cloudera][Hardy] (35) Error from server: error code:
'0' error message: 'Invalid OperationHandle: OperationHandle
[opType=GET_SCHEMAS,
getHandleIdentifier()=60809d7d-e4db-4696-8c8a-ea545094eaec]'. [Cloudera][Hardy]
(35) Error from server: error code: '0' error message: 'Invalid
OperationHandle: OperationHandle [opType=GET_SCHEMAS,
getHandleIdentifier()=60809d7d-e4db-4696-8c8a-ea545094eaec]'. [Cloudera][Hardy]
(35) Error from server: error code: '0' error message: 'Invalid
OperationHandle: OperationHandle [opType=GET_SCHEMAS,
getHandleIdentifier()=60809d7d-e4db-4696-8c8a-ea545094eaec]'.
{code}
This does not seem to present an issue when using a JDBC driver to connect and
everything works as expected.
A snippet of the haProvider config:
{code:java}
<provider>
<role>ha</role>
<name>HaProvider</name>
<enabled>true</enabled>
<param>
<name>HIVE</name>
<value>maxFailoverAttempts=3;failoverSleep=1000;maxRetryAttempts=300;retrySleep=1000;enabled=true;enableStickySession=true;noFallback=false;enableLoadBalancing=true</value>
</param>
</provider>
{code}
Using the following fix unfortunately does not rectify the problem:
[https://github.com/apache/knox/pull/481/]
was:
When configuring Knox to use the HA provider with sticky sessions and
loadbalancing enabled for Hive, using an ODBC driver to connect causes the
following error:
{code:java}
SQL Error [35] [S1000]: [Cloudera][Hardy] (35) Error from server: error code:
'0' error message: 'Invalid OperationHandle: OperationHandle
[opType=GET_SCHEMAS,
getHandleIdentifier()=60809d7d-e4db-4696-8c8a-ea545094eaec]'. [Cloudera][Hardy]
(35) Error from server: error code: '0' error message: 'Invalid
OperationHandle: OperationHandle [opType=GET_SCHEMAS,
getHandleIdentifier()=60809d7d-e4db-4696-8c8a-ea545094eaec]'. [Cloudera][Hardy]
(35) Error from server: error code: '0' error message: 'Invalid
OperationHandle: OperationHandle [opType=GET_SCHEMAS,
getHandleIdentifier()=60809d7d-e4db-4696-8c8a-ea545094eaec]'.
{code}
This does not seem to present an issue when using a JDBC driver to connect and
everything works as expected.
A snippet of the haProvider config:
{code:java}
<provider>
<role>ha</role>
<name>HaProvider</name>
<enabled>true</enabled>
<param>
<name>HIVE</name>
<value>maxFailoverAttempts=3;failoverSleep=1000;maxRetryAttempts=300;retrySleep=1000;enabled=true;enableStickySession=true;noFallback=false;enableLoadBalancing=true</value>
</param>
</provider>
{code}
Using the following fix unfortunately does not rectify the problem:
[https://github.com/apache/knox/pull/481/]
> Invalid OperationHandle error from Hive when using Knox HA and ODBC drivers
> ---------------------------------------------------------------------------
>
> Key: KNOX-2656
> URL: https://issues.apache.org/jira/browse/KNOX-2656
> Project: Apache Knox
> Issue Type: Bug
> Components: Server
> Affects Versions: 1.5.0
> Reporter: Joathan Levenson
> Priority: Major
>
> When configuring Knox to use the HA provider with sticky sessions and
> loadbalancing enabled for Hive, using an ODBC driver to connect causes the
> following error:
> {code:java}
> SQL Error [35] [S1000]: [Cloudera][Hardy] (35) Error from server: error code:
> '0' error message: 'Invalid OperationHandle: OperationHandle
> [opType=GET_SCHEMAS,
> getHandleIdentifier()=60809d7d-e4db-4696-8c8a-ea545094eaec]'.
> [Cloudera][Hardy] (35) Error from server: error code: '0' error message:
> 'Invalid OperationHandle: OperationHandle [opType=GET_SCHEMAS,
> getHandleIdentifier()=60809d7d-e4db-4696-8c8a-ea545094eaec]'.
> [Cloudera][Hardy] (35) Error from server: error code: '0' error message:
> 'Invalid OperationHandle: OperationHandle [opType=GET_SCHEMAS,
> getHandleIdentifier()=60809d7d-e4db-4696-8c8a-ea545094eaec]'.
> {code}
> This does not seem to present an issue when using a JDBC driver to connect
> and everything works as expected.
> A snippet of the haProvider config:
> {code:java}
> <provider>
> <role>ha</role>
> <name>HaProvider</name>
> <enabled>true</enabled>
> <param>
> <name>HIVE</name>
> <value>maxFailoverAttempts=3;failoverSleep=1000;maxRetryAttempts=300;retrySleep=1000;enabled=true;enableStickySession=true;noFallback=false;enableLoadBalancing=true</value>
> </param>
> </provider>
> {code}
> Using the following fix unfortunately does not rectify the problem:
> [https://github.com/apache/knox/pull/481/]
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
