None of the nodes *needs* super high performance hardware, but it will definitely benefit from it. Given the ubiquity of gigabit ethernet, you shouldn't be going for any less. 10GBe is nice if you can afford it.
Master only nodes don't need to be large, they can be simply a few CPU cores, a few GB of RAM and minimal disk - they don't hold any data. Same goes for client only nodes, though you probably want more RAM on them to allow for querying. Data only nodes are the ones you want to invest your budget in, they want fast disk for retrieval, lots of CPU for indexing and lots of RAM for both. Kibana can go on a client node. We don't recommend sending queries or indexing via master only nodes. As for testing, you really need to do that on your own use case, what you expect your data and your queries to look like. This is really domain knowledge. PS - We're moving to https://discuss.elastic.co/, please join us there for any future discussions! On 10 May 2015 at 18:11, haries fajar nugroho <[email protected]> wrote: > I have created elasticsearch cluster (5 shards, 1 replica, 65536 of > max_file_descriptors, enable mlockall,same value between es_min_mem and > es_max_mem, 1 node as master node also data node, 1 node as data only node, > 1.5-3 GB of logs/hour need to be processed). But i have some issues > crossing in my head : > > > 1. Hardware limitation (not all of my available hardwares are five star > hardware). Five star hardware means, SSD, big RAM, Gigabit interface > > So do you have any information, which is the most suitable hardware for > each of these nodes: > - master node, does this node needs SSD, big RAM, Gigabit interface ? > - data node, does this node needs SSD, big RAM, Gigabit interface ? > - client node, does this node needs SSD, big RAM, Gigabit interface ? > - for kibana, should it be connected to client node/data node/or master > node ? Until now, i only connecting my kibana to master node. > > in my understanding, data node should have SSD, big RAM, master node needs > gigabit interface, medium amount of RAM, doesn't really need SSD, and for > client node needs to have gigabit interface, no need big RAM, no need SSD. > CMIIW > > 2. Testing the configuration of my implementation. Do you have any > recommended scenario so i could know about my elasticsearch cluster > performance. How many query request that could be handle, how many index > that could be processed, how fast the query can be performed. Until now i'm > still using Bigdesk as cluster monitoring tools > > > Regards, > > -- > Please update your bookmarks! We moved to https://discuss.elastic.co/ > --- > 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/547f879b-290c-4994-9a1a-28dd6de4fad5%40googlegroups.com > <https://groups.google.com/d/msgid/elasticsearch/547f879b-290c-4994-9a1a-28dd6de4fad5%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Please update your bookmarks! We moved to https://discuss.elastic.co/ --- 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/CAEYi1X9-Phc6%3DdhuqFSrqKGb4LCs_aYpgFXYxhnP9LGSRD61DA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
