Thanks James's sharing.
Does your client node has same performance (CPU memory) as data node or
lower perf?
On Sunday, May 31, 2015 at 12:25:58 AM UTC+8, James Macdonald wrote:
If it is good enough for you, it is good enough for you. I will just give
you one anecdote: We implemented 3
Thanks!
Was looking for something more advanced, or lets say, something using more
of the new features of ES.
On Saturday, May 30, 2015 at 9:01:35 PM UTC+2, Nikolas Everett wrote:
Github. Stack overflow but their search isn't that nice the last time I
checked.
On May 30, 2015 2:53 PM,
Wikipedia too ;)
PS - We're moving to https://discuss.elastic.co/, please join us there for
any future discussions!
On 31 May 2015 at 05:01, Nikolas Everett nik9...@gmail.com wrote:
Github. Stack overflow but their search isn't that nice the last time I
checked.
On May 30, 2015 2:53 PM,
Thanks!
Was looking for something more advanced, or lets say, something using more
of the new features of ES.
On Saturday, May 30, 2015 at 9:01:35 PM UTC+2, Nikolas Everett wrote:
Github. Stack overflow but their search isn't that nice the last time I
checked.
On May 30, 2015 2:53 PM,
We use it in corporate scenarios in combination with text mining components for
intelligent search. Typical scale is 1-50 TB of source documents. Not public on
the Internet, but with Windows or website security.
Best regards,
Jürgen
--
Please update your bookmarks! We have moved to
Hi,
I just updated my ES package on debian (from packages.elastic.co repo) and
it seems it won't start from the init.d script since default logs path are
/usr/share/elasticsearch/logs. Though, it is mentionned that it should use
/var/log/elasticsearch as default path for debian when reading at
