in elasticsearch to avoid this situation?
I AM ALSO FRUSTRATED BY NO ANSWER HERE.
在 2014年10月14日星期二UTC+9下午12时43分17秒，xzer LR写道：
additional information:
The replica factor of my index is 1, which means there are only 2 copies
in the cluster.
Since I can get the data every 2 times, I guess
I need help about this, help!!!
--
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 elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web
additional information:
The replica factor of my index is 1, which means there are only 2 copies in
the cluster.
Since I can get the data every 2 times, I guess that there is one missing
copy, but how can I confirm it?
The cluster health api resports green.
--
You received this message
Is there anybody can help me with this issue?
--
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 elasticsearch+unsubscr...@googlegroups.com.
To view this discussion
I have a cluster with 3 physical servers and elasticsearch 1.2.3 installed.
I updated some data at yestoday and then today I got a strange issue:
I query data as following:
{
query: {
bool: {
must: [
{
term: {
applicationDateRouting.patentDocumentId:
I am upgrading a cluster in version 1.0.3 to 1.2.3 and I am confused by
something.
According to the description at
here:
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/setup-upgrade.html
I can disable the allocation before I started the upgrading process.
Then I
for versions prior
to 1.2
https://github.com/elasticsearch/elasticsearch/blob/master/src/main/java/org/elasticsearch/action/admin/cluster/state/ClusterStateRequest.java#L121-L124
Don't know much else about the code to comment further.
Cheers,
Ivan
On Fri, Jul 11, 2014 at 3:30 AM, xzer LR xia
being
able to use new features).
Jörg
On Mon, Jul 14, 2014 at 10:36 AM, xzer LR xia...@gmail.com javascript:
wrote:
I think I got the reason.
At first, I noticed that the row number from the exception stack is not
compatible to the client 1.2.2 source, then it exactly occurred
For some reasons, we have several separated elasticsearch clusters for our
front applicaitons. We want to upgrade our clusters' version to the newest
version but apparently it is impossible to upgrade all the clusters at the
same time, which means our single application have to connect to
AFAIK, There are three types search I can perform on elasticsearch:
1. query = which will do scoring and affect the hit
2. filter = which will not do scoring and affect the hit
3. post_filter = which will be applied on the result of query/filter and
will not affect the hit and facet
Thanks for the replies, we are now considering and discussing our balance
policy, all the information is helpful.
--
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
I am now evaluating elasticsearch as our text search solution. But the
problem is that we cannot guarantee that we can always allocate same
hardware for our cluster when new nodes are added, therefor we need a
solution to distribute the load in a smart way based on the machine power.
I read
12 matches
Mail list logo
