we use elastic for very few users (2 people that understand that the environment can be down),
so the setup doesn't require to meet production demands.
But we do have some limitations,
Our first node, that worked fine for quite some time, is doing excessive garbage collection for the present moment,
so I thought that adding another node would be a feasible solution.
Thinking it would be a walk in the park I encountered some, well, rain...
Apparently as soon as a second node comes in (on another host) elastic enforces production demands
(warning became errors).
Some reasons why we can't meet those demands:
- (foremost) we don't have root on the machines...
- the people that do have root are not keen on configuring the linux machines (we already are kind of the exception in a large organisation)
- we don't have much memory left on the single node we had (222mb) so increasing memory will only postpone the problem
- the data is on that node, maybe moving the data to a virtual machine that has more memory is a solution (but I guess it's also more postponing)
- we do want to keep the data we have until now (and it will grow (the current solution worked for about 4 months))
Is there a way to enforce development mode in a cluster with multiple hosts or does anyone see an other (preferably long-term) solution?