I see the following in the logs when I attempt to update the refresh
settings for an index. I'm running "0.20.1". Isn't index.refresh_interval
configurable?
[2013-02-20 16:12:59,115][WARN ][cluster.metadata ] [] [] ignoring
non dynamic index level settings for open indices: [index.refresh_interval]
I see the following in the logs when I attempt to update the refresh
settings for an index. I'm running "0.20.1". Isn't
index.refresh_interval configurable?
It is configurable. What command are you running?
[2013-02-20 16:12:59,115][WARN ][cluster.metadata ] ignoring non
dynamic index level settings for open indices:
[index.refresh_interval]
The current setting is 900s which is specified in an index template. The
update works on my test box but it fails on our larger cluster. The only
other update setting I've done is to set
index.routing.allocation.total_shards_per_node to 2 - which worked fine.
On Wednesday, February 20, 2013 4:49:40 PM UTC-5, Drew Raines wrote:
Telvis Calhoun Jr. wrote:
I see the following in the logs when I attempt to update the refresh
settings for an index. I'm running "0.20.1". Isn't
index.refresh_interval configurable?
It is configurable. What command are you running?
[2013-02-20 16:12:59,115][WARN ][cluster.metadata ] ignoring non
dynamic index level settings for open indices:
[index.refresh_interval]
Just to follow up. On my local 1-node cluster test I see a log
"index.shard.service updating refresh_interval from [15m] to [10s]" but on
the cluster I only see the cluster.metadata error. My setup has designated
'master' nodes with data=false, master=true and 'data' nodes with
data=true, master=false. I'm send the request to a master. The data nodes
have rivers enabled for ingest. The masters have river=none. I tried
restarting all the nodes in cluster but that didn't fix it.
The cluster state is GREEN and its indexing data fine.
On Wednesday, February 20, 2013 6:38:29 PM UTC-5, Telvis Calhoun Jr. wrote:
The current setting is 900s which is specified in an index template. The
update works on my test box but it fails on our larger cluster. The only
other update setting I've done is to set
index.routing.allocation.total_shards_per_node to 2 - which worked fine.
On Wednesday, February 20, 2013 4:49:40 PM UTC-5, Drew Raines wrote:
Telvis Calhoun Jr. wrote:
I see the following in the logs when I attempt to update the refresh
settings for an index. I'm running "0.20.1". Isn't
index.refresh_interval configurable?
It is configurable. What command are you running?
[2013-02-20 16:12:59,115][WARN ][cluster.metadata ] ignoring non
dynamic index level settings for open indices:
[index.refresh_interval]
I see the following in the logs when I attempt to update the refresh
settings for an index. I'm running "0.20.1". Isn't
index.refresh_interval configurable?
This command should work fine (and clearly does on your local
machine). I'm not quite sure how you're getting the warning, or why
it was thinking the index name was `index.refresh_interval', but
Martijn fixed a bug[1] in that exact section of code a couple weeks
ago. Any chance you can upgrade to 0.20.5 and see if it helps?
I see the following in the logs when I attempt to update the refresh
settings for an index. I'm running "0.20.1". Isn't
index.refresh_interval configurable?
This command should work fine (and clearly does on your local
machine). I'm not quite sure how you're getting the warning, or why
it was thinking the index name was `index.refresh_interval', but
Martijn fixed a bug[1] in that exact section of code a couple weeks
ago. Any chance you can upgrade to 0.20.5 and see if it helps?
I see the following in the logs when I attempt to update the refresh
settings for an index. I'm running "0.20.1". Isn't
index.refresh_interval configurable?
This command should work fine (and clearly does on your local
machine). I'm not quite sure how you're getting the warning, or why
it was thinking the index name was `index.refresh_interval', but
Martijn fixed a bug[1] in that exact section of code a couple weeks
ago. Any chance you can upgrade to 0.20.5 and see if it helps?
On Feb 22, 2013, at 5:31 PM, Telvis Calhoun Jr. <telv...@gmail.com<javascript:>>
wrote:
I'll upgrade and get back to you. Thank you for your help.
On Fri, Feb 22, 2013 at 10:25 AM, Drew Raines <aara...@gmail.com<javascript:>>
wrote:
Telvis Calhoun Jr. wrote:
I see the following in the logs when I attempt to update the
refresh
settings for an index. I'm running "0.20.1". Isn't
index.refresh_interval configurable?
This command should work fine (and clearly does on your local
machine). I'm not quite sure how you're getting the warning, or why
it was thinking the index name was `index.refresh_interval', but
Martijn fixed a bug[1] in that exact section of code a couple weeks
ago. Any chance you can upgrade to 0.20.5 and see if it helps?
--
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 elasticsearc...@googlegroups.com <javascript:>.
For more options, visit https://groups.google.com/groups/opt_out.
--
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 elasticsearc...@googlegroups.com <javascript:>.
For more options, visit https://groups.google.com/groups/opt_out.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.