I need to check if any index already exist or not or re-start or start up
the ES Data node.
I am facing issue if I restart the ES Data node and then directly check if
an index exist or not. I am always getting response as false (even if it
exist and a valid one). But if, I perform a search or any
Could anyone assist me to know how can I find a formula or guidelines to
calculate/estimate the index size created by elastic search. I found that
there is a formula (excel sheet) for it for LUCENE.
Thanks!
Gaurav
--
You received this message because you are subscribed to the Google Groups
Can't he just use two nodes as a bare minimum setup with number of replica
as one so that the search is available even if one node goes down. He can
add another node as soon as he observe any one node failure to avoid any
data loss.
...my 2 cents.
Gaurav
On Dec 27, 2014 12:16 PM, David Pilato
Per, http://thinkbiganalytics.com/solr-vs-elastic-search/ , ElasticSearch
does not suport shard spiltting which Solr supports. Is it generally an
issue in production, if yes what alternate user has :-
Shard Splitting
Shards are the partitioning unit for the Lucene index, both Solr and
.
On 21 November 2014 00:37, Gaurav gupta gupta.gaurav0...@gmail.com
wrote:
Is Elasticsearch also supported on AIX and HP Itanium 11.31. I didn't
find this information in release notes or installation instructions.
Thanks
Gaurav
--
You received this message because you are subscribed
Lucene segment files, they should get picked up - or you get nasty errors
because ES uses a custom Lucene index format and can not process standard
Lucene segments.
Jörg
On Thu, Nov 20, 2014 at 2:26 PM, Gaurav gupta gupta.gaurav0...@gmail.com
wrote:
Thanks Jorg for the guidance and I have am
but
the segments_N (segments_2 in lucene and segments_3 in ES) are slightly
different
[image: Inline image 1]
Lucene Vs ES :-
[image: Inline image 2]
Thanks
Gaurav
On Thu, Nov 27, 2014 at 8:09 PM, Gaurav gupta gupta.gaurav0...@gmail.com
wrote:
Otis,
I am not sure how many of our customers
the Lucene API to use
the Elasticsearch API and re-run the indexing process.
Jörg
On Thu, Nov 13, 2014 at 7:11 PM, Gaurav gupta gupta.gaurav0...@gmail.com
wrote:
Hi All,
I have an embedded Search Engine in our product which is based on Lucene
4.8.1 and now I would like to migrate it to latest
Is Elasticsearch also supported on AIX and HP Itanium 11.31. I didn't find
this information in release notes or installation instructions.
Thanks
Gaurav
--
You received this message because you are subscribed to the Google Groups
elasticsearch group.
To unsubscribe from this group and stop
Hi All,
I have an embedded Search Engine in our product which is based on Lucene
4.8.1 and now I would like to migrate it to latest ElasticSearch 1.4 for
better distributed support (sharding and replication, mainly). Could you
guide me how one should migrate the existing indexes created by
Hi,
Somehow the default multicast discovery is not working for me and I am
exploring the unicast discovery mechanism to set up a ES cluster on two
physical machines. I am am able to set up it using the default ES
installation on two machines with configuring the both YML files to point
to each
Kevin,
I found the recent comparision from the search experts @
http://berlinbuzzwords.de/session/side-side-elasticsearch-and-solr
It appears that ES is now a prefered choice due to better distributed
support.
cheers,
Gaurav
On Fri, Oct 3, 2014 at 8:16 AM, Kevin Burton burtona...@gmail.com
Do anybody has any thoughts on below email points.
Also, can anybody help me to locate any performance comparison between
Databases (RDBMS) vs Lucene/ES index, for insert/update/delete feature.
Thanks
On Friday, May 16, 2014 7:44:56 PM UTC+5:30, Gaurav gupta wrote:
Hi,
We are exploring
I think you need to only initialize in once on application (JVM) launch.
You can alternatively use the JAVA client API :-
Node node = nodeBuilder().node();
Client client = node.client();
Refer :-
Hi,
We are exploring the Lucene/ES as an embedded search engine inside our
product offering and while analysis following concerns come up. Could you
share your thoughts on how serious/genuine these are :-
1.Read Dominant - Data in Lucene Index is intended to be read
predominantly and not
15 matches
Mail list logo