Re: now throttling indexing
On Fri, Mar 13, 2015 at 6:09 AM, Michael McCandless m...@elastic.co wrote: That is the right setting to disable store throttling, but even without throttling writes MB/sec for merges, the merges can still fall behind, leading to index throttling. ES does this to protect the health of the index because too many segments will cause all sorts of trouble. What IO system is your index on? If you're on spinning disks you could try setting index.merge.scheduler.max_thread_count to 1 since spinning disks struggle with concurrent merges. See http://www.elastic.co/guide/en/elasticsearch/reference/current/index-modules-merge.html Also, do you leave enough (at least 50%) free RAM to the OS for buffering pages? This can make a difference with spinning disks since the OS has more freedom to do read-ahead on the files being merged... The index is on an SSD (EC2 m3.large). I'll look into what else is going on, had just noticed a few of those log entries, and thought setting `indices.store.throttle.type: none` might be a quick fix :-) -- 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 visit https://groups.google.com/d/msgid/elasticsearch/CAHte5%2B%2BqrQzoQAicwz9Q%2BMprcNVhVqXWKGp_CkKYefKNeWnO_A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
now throttling indexing
I set `indices.store.throttle.type: none` in the elasticsearch.yml, and yet this shows up in the logs: now throttling indexing: numMergesInFlight=5, maxNumMerges=4 stop throttling indexing: numMergesInFlight=3, maxNumMerges=4 Did I misunderstand the purpose of this setting? -- 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 visit https://groups.google.com/d/msgid/elasticsearch/3b0f57e1-f78e-4782-ad4d-2dfe42bb5c17%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Geohash grid aggregation broken in 1.4.0!
If you are using the geohash grid aggregation, and your index can contain documents with more than one value, you may want to hold off migrating to 1.4.0 (see comment at see https://github.com/elasticsearch/elasticsearch/issues/8512)... -- 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 visit https://groups.google.com/d/msgid/elasticsearch/5ce977ae-8e92-44a3-8f5e-ae78ba160ab9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Geohash grid aggregation broken in 1.4.0!
On Mon, Nov 17, 2014 at 10:48 AM, Eric Jain eric.j...@gmail.com wrote: If you are using the geohash grid aggregation, and your index can contain documents with more than one value, you may want to hold off migrating to 1.4.0 [...] The correct issue link is https://github.com/elasticsearch/elasticsearch/issues/8507 -- 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 visit https://groups.google.com/d/msgid/elasticsearch/CAHte5%2B%2BpCD18VVYRaeY1mMwzbz95MXPyndAdJXfDgo8CzXg9og%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: 1.4.0 data node can't join existing 1.3.4 cluster
On Fri, Nov 14, 2014 at 3:41 AM, madsmar...@colourbox.com wrote: I'm also seing this problem when a 1.4.0 node tries joining a 1.3.4 cluster with cloud-aws plugin version 2.4.0. Is there a workaround to use during upgrade, since I assume it's not a problem when they're all upgraded to 1.4.0. I ended up starting a new cluster (ignoring all the warnings logged on startup), and restoring from a snapshot. Once all the 1.3.4 nodes were gone, no issues. -- Eric Jain Got data? Get answers at zenobase.com. -- 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 visit https://groups.google.com/d/msgid/elasticsearch/CAHte5%2BJ%2BfnBnus%3DOX6itdwcaB9%2Bh_KDMwDYRBWU-4fWL0CohJA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
1.4.0 data node can't join existing 1.3.4 cluster
(using elasticsearch-cloud-aws 2.4) This should work, right? Or do I need to upgrade the cluster to 1.3.5 first? The connection fails after a few errors like: 2014-11-13 07:18:22,498 [WARN] org.elasticsearch.discovery.zen.ping.unicast - [Porcupine] failed to send ping to [[#cloud-i-b743e456-0][530-1d][inet[/10.186.145.210:9300]]] org.elasticsearch.transport.RemoteTransportException: [Nomad][inet[/10.186.145.210:9300]][internal:discovery/zen/unicast] Caused by: org.elasticsearch.transport.ActionNotFoundTransportException: No handler for action [internal:discovery/zen/unicast] at org.elasticsearch.transport.netty.MessageChannelHandler.handleRequest(MessageChannelHandler.java:210) ~[org.elasticsearch.elasticsearch-1.4.0.jar:na] at org.elasticsearch.transport.netty.MessageChannelHandler.messageReceived(MessageChannelHandler.java:111) ~[org.elasticsearch.elasticsearch-1.4.0.jar:na] at org.elasticsearch.common.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70) ~[org.elasticsearch.elasticsearch-1.4.0.jar:na] -- 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 visit https://groups.google.com/d/msgid/elasticsearch/efd3232c-b22f-4f2b-94c4-c942b75e81bf%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: 1.4.0 data node can't join existing 1.3.4 cluster
On Thu, Nov 13, 2014 at 10:05 AM, joergpra...@gmail.com joergpra...@gmail.com wrote: Do not mix 1.3 with 1.4 nodes, it does not work. If that is so, that seems like something the release notes should mention? -- 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 visit https://groups.google.com/d/msgid/elasticsearch/CAHte5%2BKyW3nZ82uf1w1C_i3O9oW%3D%3DhG7f3WUC2-g40%3DwUn5Fgw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: Replicating TermsFacet functionality with aggregations
https://github.com/elasticsearch/elasticsearch/issues/7213 On Thursday, February 13, 2014 3:31:34 PM UTC-8, Adrien Grand wrote: Indeed, I don't think this is possible with aggregations right now. Can you open an issue on Github? On Wed, Feb 12, 2014 at 6:38 PM, Brian Hudson brian.r...@gmail.com javascript: wrote: Loving aggregations so far, great work guys. I'm trying to convert some code I have which uses TermsFacet to use aggregations instead, however I am not sure how to replicate the TermFacet.getOtherCount() functionality.To replicate TermsFacet.getMissingCount() I am simply adding a missing aggregation, but I don't see any aggregation equivalent for other count. Does anyone have any suggestions on how to replicate this functionality using aggregations? Brian -- 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:. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/4931eb6f-5b30-4baf-aa42-4092ea4e6156%40googlegroups.com . For more options, visit https://groups.google.com/groups/opt_out. -- Adrien Grand -- 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 visit https://groups.google.com/d/msgid/elasticsearch/b48fb844-ab5b-4005-875d-2f84e9bae77f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Register snapshot repositories via config file?
Would it make sense to allow snapshot repositories to be registered via the config file? The docs have an example, but it's for running the tests only. repositories: s3: bucket: bucket_name region: us-west-2 -- 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 visit https://groups.google.com/d/msgid/elasticsearch/25f44dbe-34d5-4b5d-8a64-dc534b978357%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Is this link still applicable on EC2? http://www.elasticsearch.org/tutorials/elasticsearch-on-ec2/
The S3 Gateway has been dropped, so you'll either need to use EBS, or set up some mechanism to do snapshots to S3. Other than that, no major changes. On Thursday, July 24, 2014 10:12:25 PM UTC-7, vjbangis wrote: Hi, Is this link http://www.elasticsearch.org/tutorials/elasticsearch-on-ec2/still applicable on EC2, cause it's since August 2011 and the release of ES is 0.19..? But I used it as a guidelines. (http://www.elasticsearch.org/tutorials/elasticsearch-on-ec2/) -- 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 visit https://groups.google.com/d/msgid/elasticsearch/a3cd63bf-973e-414e-896b-ff600a39fb28%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: elasticsearch 1.1.1 initialization failed
This issue has been resolved with cloud-aws 2.1.1:
https://github.com/elasticsearch/elasticsearch-cloud-aws/issues/74
On Thursday, April 17, 2014 6:32:05 PM UTC-7, Eric Jain wrote:
Just tried to upgrade elasticsearch 1.1.0 to 1.1.1 (with the cloud-aws
plugin 2.1.0), and am no longer able to start any nodes:
2014-04-18 01:19:42,754 [INFO] node - [Skywalker] version[1.1.1],
pid[22901], build[f1585f0/2014-04-16T14:27:12Z]
2014-04-18 01:19:42,767 [INFO] node - [Skywalker] initializing ...
2014-04-18 01:19:42,802 [INFO] plugins - [Skywalker] loaded [cloud-aws],
sites []
2014-04-18 01:19:50,019 [ERROR] bootstrap - {1.1.1}: Initialization Failed
...
1)
NoSuchMethodError[org.elasticsearch.gateway.blobstore.BlobStoreGateway.init(Lorg/elasticsearch/common/settings/Settings;Lorg/elasticsearch/threadpool/ThreadPool;Lorg/elasticsearch/cluster/ClusterService;)V]
Anyone else see 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 on the web visit
https://groups.google.com/d/msgid/elasticsearch/cb86660c-82d1-4580-8b72-d1e78866a6c3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
elasticsearch 1.1.1 initialization failed
Just tried to upgrade elasticsearch 1.1.0 to 1.1.1 (with the cloud-aws
plugin 2.1.0), and am no longer able to start any nodes:
2014-04-18 01:19:42,754 [INFO] node - [Skywalker] version[1.1.1],
pid[22901], build[f1585f0/2014-04-16T14:27:12Z]
2014-04-18 01:19:42,767 [INFO] node - [Skywalker] initializing ...
2014-04-18 01:19:42,802 [INFO] plugins - [Skywalker] loaded [cloud-aws],
sites []
2014-04-18 01:19:50,019 [ERROR] bootstrap - {1.1.1}: Initialization Failed
...
1)
NoSuchMethodError[org.elasticsearch.gateway.blobstore.BlobStoreGateway.init(Lorg/elasticsearch/common/settings/Settings;Lorg/elasticsearch/threadpool/ThreadPool;Lorg/elasticsearch/cluster/ClusterService;)V]
Anyone else see 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 on the web visit
https://groups.google.com/d/msgid/elasticsearch/d5e85a3a-eac1-4a5e-b16d-69fa825b0ebb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: S3 gateway issues
The S3 gateway from the cloud-aws 2.1.0 plugin works fine up to elasticsearch 1.1.0, but appears to be broken with 1.1.1, see my other post. On Friday, April 11, 2014 1:01:34 AM UTC-7, David Pilato wrote: What is the cloud-aws plugin version please? -- *David Pilato* | *Technical Advocate* | *Elasticsearch.com* @dadoonet https://twitter.com/dadoonet | @elasticsearchfrhttps://twitter.com/elasticsearchfr Le 11 avril 2014 à 07:43:49, Ankur Goel (ankr...@gmail.com javascript:) a écrit: Hi David , thanks for replying , I am using version number : 1.0.0, we have AWS plugin, we have removed S3 gateway for now , will switch to local but just wanted to make sure why we are getting this error, It will be really helpful to avoid any surprises in future. On Thursday, 10 April 2014 18:11:48 UTC+5:30, Ankur Goel wrote: hi, I am using s3 gateway in a application , elastic search version 1.x , I had a strange exception while starting my nodes , please take a look Error injecting constructor, java.lang.UnsupportedOperationException at org.elasticsearch.gateway.s3.S3Gateway.init(Unknown Source) while locating org.elasticsearch.gateway.s3.S3Gateway while locating org.elasticsearch.gateway.Gateway Caused by: java.lang.UnsupportedOperationException at org.elasticsearch.cluster.metadata.RestoreMetaData$Factory.fromXContent(RestoreMetaData.java:462) at org.elasticsearch.cluster.metadata.RestoreMetaData$Factory.fromXContent(RestoreMetaData.java:400) at org.elasticsearch.cluster.metadata.MetaData$Builder.fromXContent(MetaData.java:1323) at org.elasticsearch.gateway.blobstore.BlobStoreGateway.readMetaData(BlobStoreGateway.java:213) at org.elasticsearch.gateway.blobstore.BlobStoreGateway.findLatestIndex(BlobStoreGateway.java:198) at org.elasticsearch.gateway.blobstore.BlobStoreGateway.initialize(BlobStoreGateway.java:73) at org.elasticsearch.gateway.s3.S3Gateway.init(S3Gateway.java:97) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at org.elasticsearch.common.inject.DefaultConstructionProxyFactory$1.newInstance(DefaultConstructionProxyFactory.java:54) at org.elasticsearch.common.inject.ConstructorInjector.construct(ConstructorInjector.java:86) at org.elasticsearch.common.inject.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:98) at org.elasticsearch.common.inject.FactoryProxy.get(FactoryProxy.java:52) at org.elasticsearch.common.inject.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:45) at org.elasticsearch.common.inject.InjectorImpl.callInContext(InjectorImpl.java:837) at org.elasticsearch.common.inject.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:42) at org.elasticsearch.common.inject.Scopes$1$1.get(Scopes.java:57) at org.elasticsearch.common.inject.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:45) at org.elasticsearch.common.inject.InjectorBuilder$1.call(InjectorBuilder.java:200) at org.elasticsearch.common.inject.InjectorBuilder$1.call(InjectorBuilder.java:193) at org.elasticsearch.common.inject.InjectorImpl.callInContext(InjectorImpl.java:830) at org.elasticsearch.common.inject.InjectorBuilder.loadEagerSingletons(InjectorBuilder.java:193) at org.elasticsearch.common.inject.InjectorBuilder.injectDynamically(InjectorBuilder.java:175) at org.elasticsearch.common.inject.InjectorBuilder.build(InjectorBuilder.java:110) at org.elasticsearch.common.inject.Guice.createInjector(Guice.java:93) at org.elasticsearch.common.inject.Guice.createInjector(Guice.java:70) at org.elasticsearch.common.inject.ModulesBuilder.createInjector(ModulesBuilder.java:59) at org.elasticsearch.node.internal.InternalNode.init(InternalNode.java:187) at org.elasticsearch.node.NodeBuilder.build(NodeBuilder.java:159) I am trying to understand what is happening here , the exception looks like it has happened while trying to recover index data but beyond that but I cannot get a clue , please 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 elasticsearc...@googlegroups.com javascript:. To view this discussion on the web visit
Facets multi-valued, numeric fields
For sorting, elasticsearch lets me specify how I want to deal with fields that contain multiple numeric values, so I can have elasticsearch use e.g. the max value in each document. Is there a similar option I can use when aggregating documents? For example, I might want to get the average of the max value in each document. http://stackoverflow.com/questions/22368807/facets-multi-valued-fields -- 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 visit https://groups.google.com/d/msgid/elasticsearch/fa3ab4f6-1c95-4742-85b0-a13d414163de%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Illegal character in path
Just had this error (elasticsearch 1.0.1), don't recall seeing it before: java.net.URISyntaxException: Illegal character in path at index 29: /cache/11_/seg0/index12450141[12450141].ts Should I be concerned? -- 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 visit https://groups.google.com/d/msgid/elasticsearch/34bb0d6a-598a-4ae7-9fa1-200e51da92a2%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
