Re: Reload of aux jars on HiveServer2 failing

[Shashank Pedamallu]

Just wanted to add a note that I'm using Hive-2.1.1 version.

Thanks,
Shashank

On Wed, Mar 7, 2018 at 2:57 PM, Shashank Pedamallu <
shashank.pedama...@gmail.com> wrote:

> Hi,
>
> I have a jar that is configured under hive.reloadable.aux.jars.path. Upon
> updating the jar and successful execution of *RELOAD;* command via
> Beeline, the latest jar is not getting picked up. These are the steps I
> followed:
> 0. Started hs2 process with --hiveconf hive.reloadable.aux.jars.path=
> 
> 1. Removed the *desired_jar*
> 2. Added an updated jar (that has some log statements) with same name in
> the same location as *desired_jar_absolute_path*
> 3. Connected to HS2 process via Beeline and issued a RELOAD; command
> 4. Ran a query that should have emitted a log statement as per updated
> jar. But it was not.
>
> Please note that if I did a restart of hs2 process, the latest jar is
> being picked and the log statements are getting printed.
>
> Could someone please help me if I'm not using the RELOAD command right or
> if there is a known issue surrounding it.
>
> Thanks in advance!
> - Shashank
>

Reload of aux jars on HiveServer2 failing

[Shashank Pedamallu]

Hi,

I have a jar that is configured under hive.reloadable.aux.jars.path. Upon
updating the jar and successful execution of *RELOAD;* command via Beeline,
the latest jar is not getting picked up. These are the steps I followed:
0. Started hs2 process with --hiveconf
hive.reloadable.aux.jars.path=
1. Removed the *desired_jar*
2. Added an updated jar (that has some log statements) with same name in
the same location as *desired_jar_absolute_path*
3. Connected to HS2 process via Beeline and issued a RELOAD; command
4. Ran a query that should have emitted a log statement as per updated jar.
But it was not.

Please note that if I did a restart of hs2 process, the latest jar is being
picked and the log statements are getting printed.

Could someone please help me if I'm not using the RELOAD command right or
if there is a known issue surrounding it.

Thanks in advance!
- Shashank

Re: Hive Connection to Metastore is lost frequently

[Aaryan Reddy]

folks any suggestion here ?

On Tue, Feb 27, 2018 at 11:31 AM, Aaryan Reddy 
wrote:

> Hello hive community,
>
> I am working on HDP 2.5.3 distribution that comes with packaged Apache
> Hive 1.2.1 . Every so often the hive connection to the backend metastore is
> broken throwing the below message.
>
> 2018-02-16 00:00:06,679 ERROR [pool-7-thread-76]:
>> metastore.RetryingHMSHandler (RetryingHMSHandler.java:invokeInternal(209))
>> - Retrying HMSHandler after 2000 ms (attempt 5 of 10) with error:
>> javax.jdo.JDOException: Exception thrown when executing query : SELECT
>> 'org.apache.hadoop.hive.metastore.model.MNotificationNextId' AS
>> `NUCLEUS_TYPE`,`A0`.`NEXT_EVENT_ID`,`A0`.`NNI_ID` FROM
>> `NOTIFICATION_SEQUENCE` `A0`
>> at org.datanucleus.api.jdo.NucleusJDOHelper.
>> getJDOExceptionForNucleusException(NucleusJDOHelper.java:677)
>> at org.datanucleus.api.jdo.JDOQuery.executeInternal(JDOQuery.java:388)
>
>
>
> Only option that I see is to restart the metastore/Hive service . Also we
> observed from couple of days there below error in metastore log , although
> even after restart of service i still see them .
>
> 2018-02-16 00:00:04,912 ERROR [pool-7-thread-169]:
>> server.TThreadPoolServer (TThreadPoolServer.java:run(297)) - Error
>> occurred during processing of message.
>> java.lang.RuntimeException: org.apache.thrift.transport.TTransportException:
>> Peer indicated failure: GSS initiate failed
>> at org.apache.thrift.transport.TSaslServerTransport$Factory.getTransport(
>> TSaslServerTransport.java:219)
>
>
>
> The mysql version that is used for metastore is 5.6.22 & the jdbc jar
> version used to connect the metastore to the backed Db is "
> mysql-connector-java-5.1.25.jar"
>
> Any help here is appreciated.
>
> Thanks ..
>