Although others might be able to comment, IMO you need to provide more information, eg Virtualization technology What else is running in each node. So, for comparison, this is my "lab" setup. I've been testing with approx. 1GB data that has created up to 15GB of additional metadata. I've been surprised how efficient and functional the cluster is even with its minimal resources for the amount of data it's working with almost no noticeable latencies (the current bottleneck is Host disk I/O, nothing in the Guests). I have observed <no swapping> in any of the Guests. es-hq states thus, and I have verified by running "free" in each node. node1 - 4GB ram, 20gb HDD, LXDE Desktop installed, so can run multiple consoles, web browser and more easily. Running ES, Kibana (and other web apps like es-head, es-hq), redis, logstash, netcat nodes 2-4 - 1GB RAM 20GB HDD All cloned from one so are as consistently the same as possible. All running in text mode (no Desktop) so that all stats and observations should be as unpolluted as possible Running <only> ES I'm currently running in VMware, but IMO the configuration would be fine for practically any other virtualization technology. Note that if you're running a Desktop in every node, the OS may be pushing parts of the Desktop's memory usage to swap. Tony
On Monday, February 10, 2014 9:16:58 AM UTC-8, Vahid wrote: > Hi, > > ES is running on a ubuntu 64bit in VM environment with the following > memory configuration: > > 12 gb total memory > 5 gb elasticsearch > ~3 gb other processes > and 4 gb left for OS. > > ES cluster configured with 3 nodes. > In the elasticsearch.yml bootstrap.mlockall set to true. On one of the > nodes I can see that ES is using about 1gb of swap space. > Also no warn log printed on the ES log file and only one node has this > problem. > > Is there any settings missed there? > > Many thanks, > > Vahid > -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/c33b766f-c3c5-4bda-8820-bf3eb57d625a%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
