It should but.. is it?
On Sunday, February 1, 2015 at 10:16:17 PM UTC+1, Mark Walkom wrote:
>
> Yes, it should be.
>
> On 30 January 2015 at 21:35, Ernesto Reig
> > wrote:
>
>> Any comments on this?
>>
>> On Thursday, January 29, 2015 at 5:06:12 PM UT
Any comments on this?
On Thursday, January 29, 2015 at 5:06:12 PM UTC+1, Ernesto Reig wrote:
>
> Hi all,
> This might sound a dumb question but just in case: Is the fielddata
> belonging to a given index evicted when that index is removed?
>
> Thnks
>
--
You received thi
Hi all,
This might sound a dumb question but just in case: Is the fielddata
belonging to a given index evicted when that index is removed?
Thnks
--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving
Ok, thank you very much for the answer :)
On 3 December 2014 at 12:59, Mark Walkom wrote:
> Then that's not a setting you can apply via the API, you need to edit the
> elaticsearch.yml and restart unfortunately.
>
> On 3 December 2014 at 22:31, Ernesto Reig wrote:
>
>>
> see if they are returned when you get _cluster/settings.
>
> Cluster settings are applied to the nodes, but they are not "stored' in
> the same API endpoint.
>
> On 3 December 2014 at 22:10, Ernesto Reig
> > wrote:
>
>> Hello,
>> I would like t
Hello,
I would like to update the settings of all the nodes in our cluster without
having to restart them. The settings are the following:
PUT _cluster/settings
{
"persistent" : {
"gateway.type": "local",
"gateway.recover_after_nodes": 3,
"gateway.expected_nodes": 3,
n disable it (per that link).
>
> On 3 December 2014 at 20:20, Ernesto Reig wrote:
>
>> Hi all,
>> We have a cluster of 4 nodes, and we constantly add new indexes and
>> remove old ones in a daily basis operation. We had a node down for 3 days,
>> and when starting it
Hi all,
We have a cluster of 4 nodes, and we constantly add new indexes and remove
old ones in a daily basis operation. We had a node down for 3 days, and
when starting it again it just added the indexes it had. The thing is that
the name of the new indexes we create everyday depend on the date
EST service or transport level, but
> at the respective front-end application (where one page view may trigger
> multiple Elasticsearch requests).
>
> Best regards,
> --Jürgen
>
> On 27.11.2014 13:25, Ernesto Reig wrote:
>
> Hello,
> I don´t really know how to measure
Hello,
I don´t really know how to measure the number of requests per second made
to Elasticsearch cluster. I would like to know specifically the number of
search requests per second.
If I am not wrong, the stat "query_total" in "search" increases by the
number of shards being accessed in every s
Hello, I have a requirement we need to implement and I really don´t know
how to do it or even if it is possible (maybe the solution is easy but I
just don´t know).
We have Person documents like this:
{
"id": 1,
"name": "Ernesto",
"NID": "AAA"
}
{
"id": 2,
"name": "Enrique",
"NID": "A
11 matches
Mail list logo
