hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hari Sekhon (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HIVE-20666) HiveServer2 Interactive LLAP reconnect to already running Yarn app
Date Mon, 01 Oct 2018 16:53:00 GMT

     [ https://issues.apache.org/jira/browse/HIVE-20666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Hari Sekhon updated HIVE-20666:
-------------------------------
    Description: 
Improve HiveServer2 Interactive LLAP to reconnect to already running hive llap yarn app.

Currently HiveServer2 Interactive startup may fail with the following error if it cannot
get enough containers on the queue:
{code:java}
WARN cli.LlapStatusServiceDriver: Watch timeout 200s exhausted before desired state RUNNING
is attained.
2018-10-01 16:26:55,624 - LLAP app 'llap0' in 'RUNNING_PARTIAL' state. Live Instances : '3'.
Desired Instances : '4' after 212.498996019 secs.
2018-10-01 16:26:55,624 - App state is RUNNING_PARTIAL. Live Instances : '3', Desired Instance
: '4'
2018-10-01 16:26:55,624 - LLAP app 'llap0' deployment unsuccessful.
2018-10-01 16:26:55,625 - Stopping LLAP
2018-10-01 16:26:55,625 - call[['slider', 'stop', u'llap0']] {'logoutput': True, 'user': 'hive',
'stderr': -1}{code}

I could meanwhile see 5 containers for a previous hive llap invocation in the yarn scheduler
page and this is the only HiveServer2 Interactive instance, so it appears it wasn't reconnecting
and making use of the running llap app.

  was:
Improve HiveServer2 Interactive LLAP to reconnect to already running hive llap yarn app.

Currently HiveServer2 Interactive startup may fail with the following error if it cannot
get enough containers on the queue:
{code:java}
WARN cli.LlapStatusServiceDriver: Watch timeout 200s exhausted before desired state RUNNING
is attained.
2018-10-01 16:26:55,624 - LLAP app 'llap0' in 'RUNNING_PARTIAL' state. Live Instances : '3'.
Desired Instances : '4' after 212.498996019 secs.
2018-10-01 16:26:55,624 - App state is RUNNING_PARTIAL. Live Instances : '3', Desired Instance
: '4'
2018-10-01 16:26:55,624 - LLAP app 'llap0' deployment unsuccessful.
2018-10-01 16:26:55,625 - Stopping LLAP
2018-10-01 16:26:55,625 - call[['slider', 'stop', u'llap0']] {'logoutput': True, 'user': 'hive',
'stderr': -1}{code}


> HiveServer2 Interactive LLAP reconnect to already running Yarn app
> ------------------------------------------------------------------
>
>                 Key: HIVE-20666
>                 URL: https://issues.apache.org/jira/browse/HIVE-20666
>             Project: Hive
>          Issue Type: Improvement
>          Components: HiveServer2, llap
>    Affects Versions: 1.2.1
>            Reporter: Hari Sekhon
>            Priority: Major
>
> Improve HiveServer2 Interactive LLAP to reconnect to already running hive llap yarn app.
> Currently HiveServer2 Interactive startup may fail with the following error if it cannot
get enough containers on the queue:
> {code:java}
> WARN cli.LlapStatusServiceDriver: Watch timeout 200s exhausted before desired state RUNNING
is attained.
> 2018-10-01 16:26:55,624 - LLAP app 'llap0' in 'RUNNING_PARTIAL' state. Live Instances
: '3'. Desired Instances : '4' after 212.498996019 secs.
> 2018-10-01 16:26:55,624 - App state is RUNNING_PARTIAL. Live Instances : '3', Desired
Instance : '4'
> 2018-10-01 16:26:55,624 - LLAP app 'llap0' deployment unsuccessful.
> 2018-10-01 16:26:55,625 - Stopping LLAP
> 2018-10-01 16:26:55,625 - call[['slider', 'stop', u'llap0']] {'logoutput': True, 'user':
'hive', 'stderr': -1}{code}
> I could meanwhile see 5 containers for a previous hive llap invocation in the yarn scheduler
page and this is the only HiveServer2 Interactive instance, so it appears it wasn't reconnecting
and making use of the running llap app.



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

Mime
View raw message