> even that setting is not being applied after the hive shell is started and a
> query is executed.
Are you increasing it or decreasing it?
Tez will reuse existing larger containers, instead of releasing them - reducing
the parameter has almost no effect without a session restart.
Also that
Gopal,
even that setting is not being applied after the hive shell is started and
a query is executed.
Btw, what's the difference between hive.tez.container.size and
tez.task.resource.memory.mb? Should they always be the same?
On Thu, Dec 1, 2016 at 11:56 PM, Gopal Vijayaraghavan
wrote:
>
> > s
> set tez.task.resource.memory.mb to a different value than listed in
> tez-site.xml, the query that's run doesn't seem to pick up the setting and
> instead uses the one in the config file.
Why not use the setting Hive uses in the submitted vertex?
set hive.tez.container.size=?
Cheers,
Gopal
Not really sure if this is an issue on the Hive or Tez side, but when we
open a Hive shell and set tez.task.resource.memory.mb to a different value
than listed in tez-site.xml, the query that's run doesn't seem to pick up
the setting and instead uses the one in the config file. However, if we let
t
