ttp://Elasticsearch.com>*
@dadoonet <https://twitter.com/dadoonet> | @elasticsearchfr
<https://twitter.com/elasticsearchfr> |@scrutmydocs
<https://twitter.com/scrutmydocs>
Le 14 janv. 2015 à 10:59, Umutcan <mailto:umut...@gamegos.com>> a écrit :
Hi,
I have a quest
good idea to set 1.0 first three
settings? Is there any possible problems if I change these settings?
Best,
Umutcan
--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from i
.
--
*David Pilato* | /Technical Advocate/ | *Elasticsearch.com
<http://Elasticsearch.com>*
@dadoonet <https://twitter.com/dadoonet> | @elasticsearchfr
<https://twitter.com/elasticsearchfr> |@scrutmydocs
<https://twitter.com/scrutmydocs>
Le 1 déc. 2014 à 09:21, Umutcan <
way to fix this issue without upgrade.
Is there any idea or a solution?
Thanks,
Umutcan
PS: Other nodes in the cluster have Elasticsearch 1.4.
--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop
without problems.
I don't really know much about the AWS plugin though, but a standard
cluster works in that manner.
On 19 November 2014 23:38, Umutcan <mailto:umut...@gamegos.com>> wrote:
I am using 1.4.0 version. There is nothing in the logs.
I started new master after I
indices from scratch.
I use timestamp in the index names, so indices before yesterday is still
remains in the data nodes. I want to load these indices.
On 19-11-2014 12:36, Mark Walkom wrote:
What version are you on?
Is there anything in the logs?
On 19 November 2014 18:14, Umutcan
Yes, it did and both are set to true.
But, it did not join the cluster until I shut down the old master.
On 18-11-2014 22:17, Mark Walkom wrote:
Did it join the cluster without any problems?
Is it set to master: true and data:true?
On 19 November 2014 02:29, Umutcan <mailto:u
nodes.
Is there a way to make new master node find those files and use old indices?
Thanks,
Umutcan
--
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 ela
and the older ones are 1.3.2.
Does this difference cause the problem? If I upgrade the older ones,
does this solves the issue?
I installed ES via apt-get in Ubuntu. If I upgrade the current nodes via
apt-get, does this cause problems with old indices?
Thanks,
Umutcan
--
You received this
Advocate/ | *Elasticsearch.com*
@dadoonet <https://twitter.com/dadoonet> | @elasticsearchfr
<https://twitter.com/elasticsearchfr>
Le 9 juillet 2014 à 10:45:30, Umutcan (umut...@gamegos.com
<mailto:umut...@gamegos.com>) a écrit:
Hi,
We have been testing Elasticsearch for a whi
anyone who have seen some kind of similar problem.
Thanks,
Umutcan Onal
--
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...@google
. Is there any configuration to optimize this? Do I need to
flush indices or clear cache periodically?
Thanks,
Umutcan
--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from i
So, I am wondering that is there any relationship between heap size and total
data size? Is there any formula to determine heap size based on data size?
You might want to check that you're not running out of file handles:
http://www.elasticsearch.org/tutorials/too-many-open-files/
Thanks
;
is what causes the shard fails to start.
On 02/25/2014 05:29 PM, Randy wrote:
Probably low on disc on at least one machine. Monitor disc usage. Also look in
the logs and find out what error you are getting. Report back.
Sent from my iPhone
On Feb 25, 2014, at 7:25 AM, Umutcan wrote:
Hi,
I
eventually
turns red.
So, I am wondering that is there any relationship between heap size and
total data size? Is there any formula to determine heap size based on
data size?
Thanks,
Umutcan
--
You received this message because you are subscribed to the Google Groups
"elasticsearch"
d restarted them. Then, I try to connect via
> Thrift
> > and it gives me "socket.timeout: timed out" error. I can connect to my
> > cluster without any problem using HTTP.
> >
> > Is there any additional configurations on server side or client side?
> &g
an connect to
my cluster without any problem using HTTP.
Is there any additional configurations on server side or client side?
Thanks,
Umutcan
--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and s
17 matches
Mail list logo