9238&i=8>
>
>
>
> -
> To unsubscribe, e-mail: [hidden email]
> <http://user/SendEmail.jtp?type=node&node=19238&i=9>
> For additional commands, e-mail: [hidden email]
> <http://user/SendEmail.jtp?type=node&node=19238&
OK hacking the start-slave.sh did it
On Nov 18, 2014, at 4:12 PM, Pat Ferrel wrote:
This seems to work only on a ‘worker’ not the master? So I’m back to having no
way to control cores on the master?
On Nov 18, 2014, at 3:24 PM, Pat Ferrel wrote:
Looks like I can do this by not using start-a
This seems to work only on a ‘worker’ not the master? So I’m back to having no
way to control cores on the master?
On Nov 18, 2014, at 3:24 PM, Pat Ferrel wrote:
Looks like I can do this by not using start-all.sh but starting each worker
separately passing in a '--cores n' to the master? No c
Looks like I can do this by not using start-all.sh but starting each worker
separately passing in a '--cores n' to the master? No config/env way?
On Nov 18, 2014, at 3:14 PM, Pat Ferrel wrote:
I see the default and max cores settings but these seem to control total cores
per cluster.
My cobbl
I see the default and max cores settings but these seem to control total cores
per cluster.
My cobbled together home cluster needs the Master to not use all its cores or
it may lock up (it does other things). Is there a way to control max cores used
for a particular cluster machine in standalon
