# Master CPU time

**URL:** <https://discuss.elastic.co/t/master-cpu-time/3094>\
**Category:** Elasticsearch\
**Created:** [July 13, 2010, 8:37am UTC](https://discuss.elastic.co/t/master-cpu-time/3094 "2010-07-13T08:37:16Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Zaharije](https://avatars.discourse-cdn.com/v4/letter/z/ebca7d/32.png) [@Zaharije](https://discuss.elastic.co/u/Zaharije)\
**Post date:** [July 13, 2010, 8:37am UTC](https://discuss.elastic.co/t/master-cpu-time/3094/1 "2010-07-13T08:37:16Z")

</div>

hi

is it normal to have master spent much more time on cpu during search  
than other nodes. In my case master spent 4582:00 on cpu, and nodes (7  
of them) 3478:16, 3379:40, ...

Here is configuration of ES:

name: katta

cluster:  
name: ES-test

discovery:  
type: zen  
zen:  
ping:  
unicast:  
hosts: [  
"k00:9301","k01:9302","k02:9303","k03:9304","k04:9305","k06:9306","k07:9307"  
]  
transport:  
tcp:  
port: 9300  
connections\_per\_node: 7  
network:  
host: katta

gateway:  
type: hdfs  
fs:  
location: /search-sharing  
hdfs:  
uri: hdfs://hmaster:8020  
path: /user/hadoop/elastic

index:  
store:  
type: fs  
fs:  
memory:  
enabled: false

and client java app has:

Properties props = System.getProperties();  
props.setProperty("java.net.preferIPv4Stack", "true");  
System.setProperties(props);

HashMap\<String, String\> settings = new HashMap\<String, String\>();  
settings.put("name", "es-client-test-" + option);  
settings.put("cluster.name", "ES-test");  
settings.put("discovery.type", "zen");  
settings.put("discovery.zen.ping.unicast.hosts",  
"k00:9301,k01:9302,k02:9303,k03:9304,k04:9305,k06:9306,k07:9307");  
settings.put("transport.tcp.port", port);  
settings.put("network.host", ip);

Best  
Zaharije

---

<div class="post-metadata">

**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\
**Post date:** [July 13, 2010, 8:41am UTC](https://discuss.elastic.co/t/master-cpu-time/3094/2 "2010-07-13T08:41:44Z")

</div>

The master is not involved when executing a search request. It does do more  
work than others though.

-shay.banon

p.s. You don't need to set the preferIPv4 system property anymore, thats an  
old jgroups relic.

On Tue, Jul 13, 2010 at 11:37 AM, Zaharije Pasalic \<  
[pasalic.zaharije@gmail.com](mailto:pasalic.zaharije@gmail.com)\> wrote:

> hi
> 
> is it normal to have master spent much more time on cpu during search  
> than other nodes. In my case master spent 4582:00 on cpu, and nodes (7  
> of them) 3478:16, 3379:40, ...
> 
> Here is configuration of ES:
> 
> name: katta
> 
> cluster:  
> name: ES-test
> 
> discovery:  
> type: zen  
> zen:  
> ping:  
> unicast:  
> hosts: [
> 
> "k00:9301","k01:9302","k02:9303","k03:9304","k04:9305","k06:9306","k07:9307"  
> ]  
> transport:  
> tcp:  
> port: 9300  
> connections\_per\_node: 7  
> network:  
> host: katta
> 
> gateway:  
> type: hdfs  
> fs:  
> location: /search-sharing  
> hdfs:  
> uri: hdfs://hmaster:8020  
> path: /user/hadoop/elastic
> 
> index:  
> store:  
> type: fs  
> fs:  
> memory:  
> enabled: false
> 
> and client java app has:
> 
> Properties props = System.getProperties();  
> props.setProperty("java.net.preferIPv4Stack", "true");  
> System.setProperties(props);
> 
> HashMap\<String, String\> settings = new HashMap\<String, String\>();  
> settings.put("name", "es-client-test-" + option);  
> settings.put("cluster.name", "ES-test");  
> settings.put("discovery.type", "zen");  
> settings.put("discovery.zen.ping.unicast.hosts",  
> "k00:9301,k01:9302,k02:9303,k03:9304,k04:9305,k06:9306,k07:9307");  
> settings.put("transport.tcp.port", port);  
> settings.put("network.host", ip);
> 
> Best  
> Zaharije

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 4:22am UTC](https://discuss.elastic.co/t/master-cpu-time/3094/3 "2017-07-06T04:22:22Z")

</div>

Closed on July 6, 2017, 4:22am UTC