Re: marvel shows empty dashboard
OK, interesting. Can you check the logs on one of the nodes to if there are any errors? also please double check that when the node started it logged a line similar to the following (containing marvel in the list after loaded): [2014-02-02 09:03:48,043][INFO ][plugins ] [Stonewall]loaded [marvel], sites [marvel] start a node (one is enough) On Sunday, February 2, 2014 8:50:47 AM UTC+1, Ron Sher wrote: again, using 0.90.10. This is what I did: bin/plugin -i elasticsearch/marvel/latest /etc/init.d/elasticsearch restart Did the same on a different cluster - still doesn't work. On Sun, Feb 2, 2014 at 9:45 AM, Boaz Leskes b.le...@gmail.comjavascript: wrote: Hi Ron, It looks like no data is sent. What version of ES are you running? Did you restart tES after installing the plugin? Regards, Boaz On Sun, Feb 2, 2014 at 8:27 AM, Ron Sher ron@gmail.com javascript: wrote: Tony, What do you mean by activity? Indeed I've added marvel to an already running cluster and no data is shown in the dashboard and I don't see any marvel index Ron On Fri, Jan 31, 2014 at 12:47 AM, Tony Su tony...@gmail.comjavascript: wrote: Just a FYI I just installed Marvel and I noticed you need activity for Marvel to start collecting and displaying data, even about itself. If your machines are all previously setup and data already in place, I don't know if you'd read anything. Other thing I noticed is that all ES nodes have to be the same version. So, for example if Marvel is pointing to an odd-ball ES node, there would not be any activity with any other ES node so would be blank. And, I assume that after changing ES versions you restarted the ES services on every node? Otherwise you're still stuck on the previous version. HTH, Tony On Thursday, January 30, 2014 11:24:11 AM UTC-8, Brad Jordan wrote: I keep getting this alert: *No results* There were no results because no indices were found that match your selected time span. -Brad On Thursday, January 30, 2014 12:23:04 PM UTC-7, Brad Jordan wrote: Upgraded my cluster to 0.9.10 and still get a blank Marvel dashboard... I have about 30 indexes which all have data starting on about 1/20/2014 going back to 5/01/2013. Bigdesk and the Head plugin have no problems seeing that nodes, shards, indexes. Is there an additional step I'm missing? -Brad On Thursday, January 30, 2014 10:48:04 AM UTC-7, Brad Jordan wrote: Thanks! On Thursday, January 30, 2014 10:43:35 AM UTC-7, Boaz Leskes wrote: Hi brad, You should upgrade to 0.90.10. 0.90.7 is not supported by marvel. Cheers, Boaz On Thu, Jan 30, 2014 at 6:39 PM, Brad Jordan climb...@gmail.comwrote: I also have the same issue. I'm running elasticsearch-0.90.7. I installed the plugin, bounced the cluster and Marvel is just blank. Is there a config I'm missing? -Brad On Thursday, January 30, 2014 5:22:03 AM UTC-7, Ron Sher wrote: Hey, Just tried installing the plugin. Installation was easy (bin/plugin -i elasticsearch/marvel/latest followed by a restart) by then the plugin shows an empty dashboard. Am I missing something?\ Thanks, Ron -- You received this message because you are subscribed to a topic in the Google Groups elasticsearch group. To unsubscribe from this topic, visit https://groups.google.com/d/ topic/elasticsearch/UPBMKvxwwM8/unsubscribe. To unsubscribe from this group and all its topics, send an email to elasticsearc...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/4dcf998b- 89fe-4f07-bb2d-a036cd567c66%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to a topic in the Google Groups elasticsearch group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/elasticsearch/UPBMKvxwwM8/unsubscribe . To unsubscribe from this group and all its topics, send an email to elasticsearc...@googlegroups.com javascript:. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/43083c5a-bc16-4f01-8450-15402e82d798%40googlegroups.com . For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to a topic in the Google Groups elasticsearch group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/elasticsearch/UPBMKvxwwM8/unsubscribe. To unsubscribe from this group and all its topics, send an email to elasticsearc...@googlegroups.com javascript:. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAKHuyJr7%3Deh-s85HrwTjmKJ7wTcezU4aiSQG6P8vC2zFd2OD-w%40mail.gmail.com . For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed
Re: A couple Marvel Overview Q - How CPU and Memory for a Cluster are calculated
Hi Tony, The cluster summary shows a snapshot of the cluster, taken every 5 second. The CPU numer is the total cpu usage of all the ES processes (100% == one core). Memory is the total memory used by the JVM nodes the total memory available to them. Cheers, Boaz On Saturday, February 1, 2014 12:03:32 AM UTC+1, Tony Su wrote: Hello, Have posted a screenshot of Marvel on my demo cluster https://github.com/putztzu/Misc_images/blob/master/marvel_only.png FYI Configuration All nodes running on openSUSE 13.1/openjdk1.7 (On a single machine running VMware) ES-Marvel-openSUSE ES-LogstasthIndexer-Redis-LogstashShipper(ApacheParse)-netcat ELASTICSEARCH-1 ES ELASTICSEARCH-2 ES ELASTICSEARCH-3 ES ELASTICSEARCH-4 ES Questions I have about what Marvel is displaying Cluster Summary 1. CPU usage of a cluster is interesting, is it an aggregate of cluster CPU resources, and is it supposed to be a realtime snaphot or mean/median/average/something else? 2. Memory, similar Q to (1). Is this the aggregated cluster resources, total available and used, and is it current, peak or something else? Thx, Tony -- 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/e3986543-cb52-4807-b756-35ecb286720b%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: cant create cluster on ec2
If this is what you mean my trace in the logs at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.processConnectTimeout(NioClientBoss.java:137) at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:83) at org.elasticsearch.common.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:318) at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:42) at org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) at org.elasticsearch.common.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42) ... 3 more [2014-01-27 16:58:49,706][TRACE][discovery.zen.ping.unicast] [Administrator] [1] failed to connect to [#cloud-i-ef763797-0][aws-elasticsearch-east-development-20140127160434][inet[/10.198.91.74:9300]] org.elasticsearch.transport.ConnectTransportException: [][inet[/10.198.91.74:9300]] connect_timeout[30s] at org.elasticsearch.transport.netty.NettyTransport.connectToChannelsLight(NettyTransport.java:676) at org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:636) at org.elasticsearch.transport.netty.NettyTransport.connectToNodeLight(NettyTransport.java:603) at org.elasticsearch.transport.TransportService.connectToNodeLight(TransportService.java:133) at org.elasticsearch.discovery.zen.ping.unicast.UnicastZenPing$3.run(UnicastZenPing.java:278) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:701) Caused by: org.elasticsearch.common.netty.channel.ConnectTimeoutException: connection timed out: /10.239.36.98:9300 at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.processConnectTimeout(NioClientBoss.java:137) at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:83) at org.elasticsearch.common.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:318) at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:42) at org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) at org.elasticsearch.common.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42) ... 3 more [2014-01-27 16:58:49,707][TRACE][discovery.zen.ping.unicast] [Administrator] [1] failed to connect to [#cloud-i-0598a260-0][aws-elasticsearch-east-development-20140127160434][inet[/10.244.178.236:9300]] org.elasticsearch.transport.ConnectTransportException: [][inet[/10.244.178.236:9300]] connect_timeout[30s] at org.elasticsearch.transport.netty.NettyTransport.connectToChannelsLight(NettyTransport.java:676) at org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:636) at org.elasticsearch.transport.netty.NettyTransport.connectToNodeLight(NettyTransport.java:603) at org.elasticsearch.transport.TransportService.connectToNodeLight(TransportService.java:133) at org.elasticsearch.discovery.zen.ping.unicast.UnicastZenPing$3.run(UnicastZenPing.java:278) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:701) Caused by: org.elasticsearch.common.netty.channel.ConnectTimeoutException: connection timed out: /10.239.36.98:9300 at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.processConnectTimeout(NioClientBoss.java:137) at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:83) at org.elasticsearch.common.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:318) at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:42) at org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) at org.elasticsearch.common.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42) ... 3 more [2014-01-27 16:58:49,708][TRACE][discovery.zen.ping.unicast] [Administrator] [1] failed to connect to [#cloud-i-1079ac6b-0][aws-elasticsearch-east-development-20140127160434][inet[/10.211.29.210:9300]] org.elasticsearch.transport.ConnectTransportException: [][inet[/10.211.29.210:9300]] connect_timeout[30s] at org.elasticsearch.transport.netty.NettyTransport.connectToChannelsLight(NettyTransport.java:676) at
Re: There were no results because no indices were found that match your selected time span
Okay, thanks! On Tuesday, January 28, 2014 8:53:27 PM UTC+1, David Pilato wrote: Should work from 0.90.9. -- *David Pilato* | *Technical Advocate* | *Elasticsearch.com* @dadoonet https://twitter.com/dadoonet | @elasticsearchfrhttps://twitter.com/elasticsearchfr Le 28 janvier 2014 at 20:51:14, Thomas Ardal (thoma...@gmail.comjavascript:) a écrit: I know and that's the plan. But with 1.0.0 right around the corner and a lot of data to migrate, I'll probably wait for that one. Does Marvel only support the most recent versions of ES? On Tuesday, January 28, 2014 8:43:26 PM UTC+1, David Pilato wrote: 0.90.1? You should update to 0.90.10. -- David ;-) Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs Le 28 janv. 2014 à 20:11, Thomas Ardal thoma...@gmail.com a écrit : As bonus info I'm running Elasticsearch 0.90.1 on windows server 2012. I'm using the Jetty plugin to force https and basic authentication, but are accessing Marvel from localhost through http. My browser asks me for credentials when opening the Marvel url, so it could be caused by the basic authentication setup. Or? On Tuesday, January 28, 2014 8:01:21 PM UTC+1, Thomas Ardal wrote: When trying out Marvel on my Elasticsearch installation, I get the error There were no results because no indices were found that match your selected time span in the top of the page. If I understand the documentation, Marvel automatically collects statistics from all indexes on the node. What am I doing wrong? -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/7255ee52-5101-4942-8abd-b29642035237%40googlegroups.com . 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:. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/8bee9ba2-d0bf-42c3-b8ac-2c45707b9f96%40googlegroups.com . 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 elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/c2e396aa-7fcb-4257-ba10-c5b89827f662%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Incorrect document about an aggregation value_count type?
Hi Jun, It seems you are correct. Please open an issue on this as either the documentation needs to be changed or the functionality implemented. Cheers, Boaz On Friday, January 31, 2014 4:43:26 PM UTC+1, Jun Ohtani wrote: Hi, When I read the aggregation document, I found typo in the following page. http://www.elasticsearch.org/guide/en/elasticsearch/reference/master/search-aggregations-metrics-valuecount-aggregation.html#_script_7 Description : ”Counting the values generated by a script: But, I think value_count does not support script, because I don’t find “script” in ValueCountParser.java https://github.com/elasticsearch/elasticsearch/blob/2df42e4460fa5f0d87363672e305c88d9f30b093/src/main/java/org/elasticsearch/search/aggregations/metrics/valuecount/ValueCountParser.java#L54 Does it make sense? Jun Ohtani joh...@gmail.com javascript: blog : http://blog.johtani.info twitter : http://twitter.com/johtani -- 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/086d5cbc-7884-4f2f-a564-a83e42b6fe92%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: marvel shows empty dashboard
This is what I see in the log after the restart: STATUS | wrapper | 2014/02/02 11:26:54 | Copyright (C) 1999-2011 Tanuki Software, Ltd. All Rights Reserved. STATUS | wrapper | 2014/02/02 11:26:54 | http://wrapper.tanukisoftware.com STATUS | wrapper | 2014/02/02 11:26:54 | WARN | wrapper | 2014/02/02 11:26:54 | Encountered an invalid numerical value for configuration property wrapper.java.initmemory=%ES_HEAP_SIZE%. Resolving to 0. WARN | wrapper | 2014/02/02 11:26:54 | Encountered an invalid numerical value for configuration property wrapper.java.maxmemory=%ES_HEAP_SIZE%. Resolving to 0. STATUS | wrapper | 2014/02/02 11:26:54 | Launching a JVM... INFO | jvm 1| 2014/02/02 11:26:55 | WrapperManager: Initializing... INFO | jvm 1| 2014/02/02 11:27:01 | log4j:WARN No appenders could be found for logger (node). INFO | jvm 1| 2014/02/02 11:27:01 | log4j:WARN Please initialize the log4j system properly. INFO | jvm 1| 2014/02/02 11:27:01 | log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. On Sun, Feb 2, 2014 at 10:05 AM, Boaz Leskes b.les...@gmail.com wrote: OK, interesting. Can you check the logs on one of the nodes to if there are any errors? also please double check that when the node started it logged a line similar to the following (containing marvel in the list after loaded): [2014-02-02 09:03:48,043][INFO ][plugins ] [Stonewall]loaded [marvel], sites [marvel] start a node (one is enough) On Sunday, February 2, 2014 8:50:47 AM UTC+1, Ron Sher wrote: again, using 0.90.10. This is what I did: bin/plugin -i elasticsearch/marvel/latest /etc/init.d/elasticsearch restart Did the same on a different cluster - still doesn't work. On Sun, Feb 2, 2014 at 9:45 AM, Boaz Leskes b.le...@gmail.com wrote: Hi Ron, It looks like no data is sent. What version of ES are you running? Did you restart tES after installing the plugin? Regards, Boaz On Sun, Feb 2, 2014 at 8:27 AM, Ron Sher ron@gmail.com wrote: Tony, What do you mean by activity? Indeed I've added marvel to an already running cluster and no data is shown in the dashboard and I don't see any marvel index Ron On Fri, Jan 31, 2014 at 12:47 AM, Tony Su tony...@gmail.com wrote: Just a FYI I just installed Marvel and I noticed you need activity for Marvel to start collecting and displaying data, even about itself. If your machines are all previously setup and data already in place, I don't know if you'd read anything. Other thing I noticed is that all ES nodes have to be the same version. So, for example if Marvel is pointing to an odd-ball ES node, there would not be any activity with any other ES node so would be blank. And, I assume that after changing ES versions you restarted the ES services on every node? Otherwise you're still stuck on the previous version. HTH, Tony On Thursday, January 30, 2014 11:24:11 AM UTC-8, Brad Jordan wrote: I keep getting this alert: *No results* There were no results because no indices were found that match your selected time span. -Brad On Thursday, January 30, 2014 12:23:04 PM UTC-7, Brad Jordan wrote: Upgraded my cluster to 0.9.10 and still get a blank Marvel dashboard... I have about 30 indexes which all have data starting on about 1/20/2014 going back to 5/01/2013. Bigdesk and the Head plugin have no problems seeing that nodes, shards, indexes. Is there an additional step I'm missing? -Brad On Thursday, January 30, 2014 10:48:04 AM UTC-7, Brad Jordan wrote: Thanks! On Thursday, January 30, 2014 10:43:35 AM UTC-7, Boaz Leskes wrote: Hi brad, You should upgrade to 0.90.10. 0.90.7 is not supported by marvel. Cheers, Boaz On Thu, Jan 30, 2014 at 6:39 PM, Brad Jordan climb...@gmail.comwrote: I also have the same issue. I'm running elasticsearch-0.90.7. I installed the plugin, bounced the cluster and Marvel is just blank. Is there a config I'm missing? -Brad On Thursday, January 30, 2014 5:22:03 AM UTC-7, Ron Sher wrote: Hey, Just tried installing the plugin. Installation was easy (bin/plugin -i elasticsearch/marvel/latest followed by a restart) by then the plugin shows an empty dashboard. Am I missing something?\ Thanks, Ron -- You received this message because you are subscribed to a topic in the Google Groups elasticsearch group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/elasticsearch/UPBMKvxwwM8/ unsubscribe. To unsubscribe from this group and all its topics, send an email to elasticsearc...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/4dcf998b-89f e-4f07-bb2d-a036cd567c66%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to a topic in the Google Groups elasticsearch group. To unsubscribe from this topic,
Re: marvel shows empty dashboard
I've noticed that I didn't have a logging.yml (was called logging.xml instead). Changed that and then I see: [2014-02-02 15:42:19,824][ERROR][marvel.agent.exporter] error sending data java.io.FileNotFoundException: http://localhost:9200/_bulk atsun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1623) at org.elasticsearch.marvel.agent.exporter.ESExporter. sendCloseExportingConnection(ESExporter.java:232) at org.elasticsearch.marvel.agent.exporter.ESExporter.exportXContent (ESExporter.java:252) at org.elasticsearch.marvel.agent.exporter.ESExporter. exportClusterStats(ESExporter.java:172) at org.elasticsearch.marvel.agent.AgentService$ExportingWorker. exportClusterStats(AgentService.java:214) at org.elasticsearch.marvel.agent.AgentService$ExportingWorker.run( AgentService.java:180) at java.lang.Thread.run(Thread.java:724) What now? On Sun, Feb 2, 2014 at 11:29 AM, Ron Sher ron.s...@gmail.com wrote: This is what I see in the log after the restart: STATUS | wrapper | 2014/02/02 11:26:54 | Copyright (C) 1999-2011 Tanuki Software, Ltd. All Rights Reserved. STATUS | wrapper | 2014/02/02 11:26:54 | http://wrapper.tanukisoftware.com STATUS | wrapper | 2014/02/02 11:26:54 | WARN | wrapper | 2014/02/02 11:26:54 | Encountered an invalid numerical value for configuration property wrapper.java.initmemory=%ES_HEAP_SIZE%. Resolving to 0. WARN | wrapper | 2014/02/02 11:26:54 | Encountered an invalid numerical value for configuration property wrapper.java.maxmemory=%ES_HEAP_SIZE%. Resolving to 0. STATUS | wrapper | 2014/02/02 11:26:54 | Launching a JVM... INFO | jvm 1| 2014/02/02 11:26:55 | WrapperManager: Initializing... INFO | jvm 1| 2014/02/02 11:27:01 | log4j:WARN No appenders could be found for logger (node). INFO | jvm 1| 2014/02/02 11:27:01 | log4j:WARN Please initialize the log4j system properly. INFO | jvm 1| 2014/02/02 11:27:01 | log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. On Sun, Feb 2, 2014 at 10:05 AM, Boaz Leskes b.les...@gmail.com wrote: OK, interesting. Can you check the logs on one of the nodes to if there are any errors? also please double check that when the node started it logged a line similar to the following (containing marvel in the list after loaded): [2014-02-02 09:03:48,043][INFO ][plugins ] [Stonewall]loaded [marvel], sites [marvel] start a node (one is enough) On Sunday, February 2, 2014 8:50:47 AM UTC+1, Ron Sher wrote: again, using 0.90.10. This is what I did: bin/plugin -i elasticsearch/marvel/latest /etc/init.d/elasticsearch restart Did the same on a different cluster - still doesn't work. On Sun, Feb 2, 2014 at 9:45 AM, Boaz Leskes b.le...@gmail.com wrote: Hi Ron, It looks like no data is sent. What version of ES are you running? Did you restart tES after installing the plugin? Regards, Boaz On Sun, Feb 2, 2014 at 8:27 AM, Ron Sher ron@gmail.com wrote: Tony, What do you mean by activity? Indeed I've added marvel to an already running cluster and no data is shown in the dashboard and I don't see any marvel index Ron On Fri, Jan 31, 2014 at 12:47 AM, Tony Su tony...@gmail.com wrote: Just a FYI I just installed Marvel and I noticed you need activity for Marvel to start collecting and displaying data, even about itself. If your machines are all previously setup and data already in place, I don't know if you'd read anything. Other thing I noticed is that all ES nodes have to be the same version. So, for example if Marvel is pointing to an odd-ball ES node, there would not be any activity with any other ES node so would be blank. And, I assume that after changing ES versions you restarted the ES services on every node? Otherwise you're still stuck on the previous version. HTH, Tony On Thursday, January 30, 2014 11:24:11 AM UTC-8, Brad Jordan wrote: I keep getting this alert: *No results* There were no results because no indices were found that match your selected time span. -Brad On Thursday, January 30, 2014 12:23:04 PM UTC-7, Brad Jordan wrote: Upgraded my cluster to 0.9.10 and still get a blank Marvel dashboard... I have about 30 indexes which all have data starting on about 1/20/2014 going back to 5/01/2013. Bigdesk and the Head plugin have no problems seeing that nodes, shards, indexes. Is there an additional step I'm missing? -Brad On Thursday, January 30, 2014 10:48:04 AM UTC-7, Brad Jordan wrote: Thanks! On Thursday, January 30, 2014 10:43:35 AM UTC-7, Boaz Leskes wrote: Hi brad, You should upgrade to 0.90.10. 0.90.7 is not supported by marvel. Cheers, Boaz On Thu, Jan 30, 2014 at 6:39 PM, Brad Jordan climb...@gmail.comwrote: I also have the same issue. I'm running elasticsearch-0.90.7. I installed the plugin, bounced the cluster and Marvel is just blank. Is
Re: marvel shows empty dashboard
The beginning of the log looks like:
[2014-02-02 15:38:56,003][INFO ][node ] [hades3] version
[0.90.10], pid[20219], build[0a5781f/2014-01-10T10:18:37Z]
[2014-02-02 15:38:56,004][INFO ][node ] [hades3]
initializing ...
[2014-02-02 15:38:56,027][INFO ][plugins ] [hades3] loaded
[marvel], sites [marvel, head]
[2014-02-02 15:39:01,302][INFO ][node ] [hades3]
initialized
[2014-02-02 15:39:01,302][INFO ][node ] [hades3]
starting ...
[2014-02-02 15:39:01,410][INFO ][transport] [hades3]
bound_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish_address {inet[/
192.168.10.148:9300]}
[2014-02-02 15:39:06,408][ERROR][marvel.agent.exporter] error sending
data
java.io.FileNotFoundException: http://localhost:9200/_bulk
atsun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1623)
at org.elasticsearch.marvel.agent.exporter.ESExporter.
sendCloseExportingConnection(ESExporter.java:232)
at org.elasticsearch.marvel.agent.exporter.ESExporter.exportXContent
(ESExporter.java:252)
at org.elasticsearch.marvel.agent.exporter.ESExporter.
exportNodeStats(ESExporter.java:134)
at org.elasticsearch.marvel.agent.AgentService$ExportingWorker.
exportNodeStats(AgentService.java:274)
at org.elasticsearch.marvel.agent.AgentService$ExportingWorker.run(
AgentService.java:174)
at java.lang.Thread.run(Thread.java:724)
On Sun, Feb 2, 2014 at 3:43 PM, Ron Sher ron.s...@gmail.com wrote:
I've noticed that I didn't have a logging.yml (was called logging.xml
instead).
Changed that and then I see:
[2014-02-02 15:42:19,824][ERROR][marvel.agent.exporter] error sending
data
java.io.FileNotFoundException: http://localhost:9200/_bulk
atsun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1623)
at org.elasticsearch.marvel.agent.exporter.ESExporter.
sendCloseExportingConnection(ESExporter.java:232)
at org.elasticsearch.marvel.agent.exporter.ESExporter.
exportXContent(ESExporter.java:252)
at org.elasticsearch.marvel.agent.exporter.ESExporter.
exportClusterStats(ESExporter.java:172)
at org.elasticsearch.marvel.agent.AgentService$ExportingWorker.
exportClusterStats(AgentService.java:214)
at org.elasticsearch.marvel.agent.AgentService$ExportingWorker.run
(AgentService.java:180)
at java.lang.Thread.run(Thread.java:724)
What now?
On Sun, Feb 2, 2014 at 11:29 AM, Ron Sher ron.s...@gmail.com wrote:
This is what I see in the log after the restart:
STATUS | wrapper | 2014/02/02 11:26:54 | Copyright (C) 1999-2011
Tanuki Software, Ltd. All Rights Reserved.
STATUS | wrapper | 2014/02/02 11:26:54 |
http://wrapper.tanukisoftware.com
STATUS | wrapper | 2014/02/02 11:26:54 |
WARN | wrapper | 2014/02/02 11:26:54 | Encountered an invalid
numerical value for configuration property
wrapper.java.initmemory=%ES_HEAP_SIZE%.
Resolving to 0.
WARN | wrapper | 2014/02/02 11:26:54 | Encountered an invalid
numerical value for configuration property
wrapper.java.maxmemory=%ES_HEAP_SIZE%.
Resolving to 0.
STATUS | wrapper | 2014/02/02 11:26:54 | Launching a JVM...
INFO | jvm 1| 2014/02/02 11:26:55 | WrapperManager: Initializing...
INFO | jvm 1| 2014/02/02 11:27:01 | log4j:WARN No appenders could
be found for logger (node).
INFO | jvm 1| 2014/02/02 11:27:01 | log4j:WARN Please initialize
the log4j system properly.
INFO | jvm 1| 2014/02/02 11:27:01 | log4j:WARN See
http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
On Sun, Feb 2, 2014 at 10:05 AM, Boaz Leskes b.les...@gmail.com wrote:
OK, interesting.
Can you check the logs on one of the nodes to if there are any errors?
also please double check that when the node started it logged a line
similar to the following (containing marvel in the list after loaded):
[2014-02-02 09:03:48,043][INFO ][plugins ]
[Stonewall]loaded
[marvel], sites [marvel]
start a node (one is enough)
On Sunday, February 2, 2014 8:50:47 AM UTC+1, Ron Sher wrote:
again, using 0.90.10.
This is what I did:
bin/plugin -i elasticsearch/marvel/latest
/etc/init.d/elasticsearch restart
Did the same on a different cluster - still doesn't work.
On Sun, Feb 2, 2014 at 9:45 AM, Boaz Leskes b.le...@gmail.com wrote:
Hi Ron,
It looks like no data is sent. What version of ES are you running? Did
you restart tES after installing the plugin?
Regards,
Boaz
On Sun, Feb 2, 2014 at 8:27 AM, Ron Sher ron@gmail.com wrote:
Tony,
What do you mean by activity?
Indeed I've added marvel to an already running cluster and no data
is shown in the dashboard and I don't see any marvel index
Ron
On Fri, Jan 31, 2014 at 12:47 AM, Tony Su tony...@gmail.com wrote:
Just a FYI
I just installed Marvel and I noticed you need activity for Marvel
Re: Improving Bulk Indexing
What is the default of JVM 64 MB limit? Elasticsearch uses by default 1 GB heap, not 64 MB. Maybe you have an extra JVM with your bulk client that uses 64 MB? This is much too few. Use 4-6 GB heap if your machine allows that. Note, JVM 7 of OpenJDK/Oracle, which is recommended, uses 25% of your host RAM by default for your heap, not 64 MB. 1. You can use the BulkProcessor in the Java API which also has a volume chunk limit instead of doc num, the default is 5 MB. 64 MB is a very large bulk size. Bulk sizes of ~2GB are very bad since that will thrash all the heap on the ES nodes and this induces severe GC problems and delays. I recommend 1-10 MB, so each bulk responds within 1 second, and GC is very fast. You can run bulks concurrently to increase speed. To find the sweet spot of your client/server situation, you have to experiment with your setup: choose 1MB and 1 concurrent thread, then 2MB and 1 concurrent thread, 2MB / 2 threads etc. until you see rates declining. ES has some internal settings that avoid an overrun of the whole cluster. 2. Most important is to set replica to 0 to make place for better performance while bulk indexing, and disable the refresh rate of default 1sec to -1. After bulk, re-enable refresh, optimize, and add replica. There are other more advanced knobs like throttling at store level or thread pool or queue sizes but changing the defaults do not influence bulk performance that much. Jörg -- 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/CAKdsXoHJUaqonj7G50zNQ_xU6Prbw3GXayFTGwp-o11FdHr3cw%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: marvel shows empty dashboard
It looks like marvel can't store the data on localhost:9200. The most common
reason is running on another port. Another option is that ES is not bound on
localhost or that http access is turned off (in which case marvel won't work).
Can you verify you can connect ES via the terminal while on the machine itself?
If needed you can change the host port marvel where sends data to. See
http://www.elasticsearch.org/guide/en/marvel/current/index.html#stats-export
On Sun, Feb 2, 2014 at 3:23 PM, Ron Sher ron.s...@gmail.com wrote:
The beginning of the log looks like:
[2014-02-02 15:38:56,003][INFO ][node ] [hades3] version
[0.90.10], pid[20219], build[0a5781f/2014-01-10T10:18:37Z]
[2014-02-02 15:38:56,004][INFO ][node ] [hades3]
initializing ...
[2014-02-02 15:38:56,027][INFO ][plugins ] [hades3] loaded
[marvel], sites [marvel, head]
[2014-02-02 15:39:01,302][INFO ][node ] [hades3]
initialized
[2014-02-02 15:39:01,302][INFO ][node ] [hades3]
starting ...
[2014-02-02 15:39:01,410][INFO ][transport] [hades3]
bound_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish_address {inet[/
192.168.10.148:9300]}
[2014-02-02 15:39:06,408][ERROR][marvel.agent.exporter] error sending
data
java.io.FileNotFoundException: http://localhost:9200/_bulk
atsun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1623)
at org.elasticsearch.marvel.agent.exporter.ESExporter.
sendCloseExportingConnection(ESExporter.java:232)
at org.elasticsearch.marvel.agent.exporter.ESExporter.exportXContent
(ESExporter.java:252)
at org.elasticsearch.marvel.agent.exporter.ESExporter.
exportNodeStats(ESExporter.java:134)
at org.elasticsearch.marvel.agent.AgentService$ExportingWorker.
exportNodeStats(AgentService.java:274)
at org.elasticsearch.marvel.agent.AgentService$ExportingWorker.run(
AgentService.java:174)
at java.lang.Thread.run(Thread.java:724)
On Sun, Feb 2, 2014 at 3:43 PM, Ron Sher ron.s...@gmail.com wrote:
I've noticed that I didn't have a logging.yml (was called logging.xml
instead).
Changed that and then I see:
[2014-02-02 15:42:19,824][ERROR][marvel.agent.exporter] error sending
data
java.io.FileNotFoundException: http://localhost:9200/_bulk
atsun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1623)
at org.elasticsearch.marvel.agent.exporter.ESExporter.
sendCloseExportingConnection(ESExporter.java:232)
at org.elasticsearch.marvel.agent.exporter.ESExporter.
exportXContent(ESExporter.java:252)
at org.elasticsearch.marvel.agent.exporter.ESExporter.
exportClusterStats(ESExporter.java:172)
at org.elasticsearch.marvel.agent.AgentService$ExportingWorker.
exportClusterStats(AgentService.java:214)
at org.elasticsearch.marvel.agent.AgentService$ExportingWorker.run
(AgentService.java:180)
at java.lang.Thread.run(Thread.java:724)
What now?
On Sun, Feb 2, 2014 at 11:29 AM, Ron Sher ron.s...@gmail.com wrote:
This is what I see in the log after the restart:
STATUS | wrapper | 2014/02/02 11:26:54 | Copyright (C) 1999-2011
Tanuki Software, Ltd. All Rights Reserved.
STATUS | wrapper | 2014/02/02 11:26:54 |
http://wrapper.tanukisoftware.com
STATUS | wrapper | 2014/02/02 11:26:54 |
WARN | wrapper | 2014/02/02 11:26:54 | Encountered an invalid
numerical value for configuration property
wrapper.java.initmemory=%ES_HEAP_SIZE%.
Resolving to 0.
WARN | wrapper | 2014/02/02 11:26:54 | Encountered an invalid
numerical value for configuration property
wrapper.java.maxmemory=%ES_HEAP_SIZE%.
Resolving to 0.
STATUS | wrapper | 2014/02/02 11:26:54 | Launching a JVM...
INFO | jvm 1| 2014/02/02 11:26:55 | WrapperManager: Initializing...
INFO | jvm 1| 2014/02/02 11:27:01 | log4j:WARN No appenders could
be found for logger (node).
INFO | jvm 1| 2014/02/02 11:27:01 | log4j:WARN Please initialize
the log4j system properly.
INFO | jvm 1| 2014/02/02 11:27:01 | log4j:WARN See
http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
On Sun, Feb 2, 2014 at 10:05 AM, Boaz Leskes b.les...@gmail.com wrote:
OK, interesting.
Can you check the logs on one of the nodes to if there are any errors?
also please double check that when the node started it logged a line
similar to the following (containing marvel in the list after loaded):
[2014-02-02 09:03:48,043][INFO ][plugins ]
[Stonewall]loaded
[marvel], sites [marvel]
start a node (one is enough)
On Sunday, February 2, 2014 8:50:47 AM UTC+1, Ron Sher wrote:
again, using 0.90.10.
This is what I did:
bin/plugin -i elasticsearch/marvel/latest
/etc/init.d/elasticsearch restart
Did the same on a different cluster - still doesn't work.
On Sun, Feb 2, 2014 at 9:45 AM, Boaz Leskes
Re: marvel shows empty dashboard
Getting somewhere...
Changed the hosts and now I get the following:
type[cluster_stats] missing: trying to auto create mapping, but dynamic
mapping is disabled
On Sun, Feb 2, 2014 at 5:26 PM, Boaz Leskes b.les...@gmail.com wrote:
It looks like marvel can't store the data on localhost:9200. The most
common reason is running on another port. Another option is that ES is not
bound on localhost or that http access is turned off (in which case marvel
won't work).
Can you verify you can connect ES via the terminal while on the machine
itself? If needed you can change the host port marvel where sends data
to. See
http://www.elasticsearch.org/guide/en/marvel/current/index.html#stats-export
On Sun, Feb 2, 2014 at 3:23 PM, Ron Sher ron.s...@gmail.com wrote:
The beginning of the log looks like:
[2014-02-02 15:38:56,003][INFO ][node ] [hades3]
version[0.90.10], pid[20219], build[0a5781f/2014-01-10T10:18:37Z]
[2014-02-02 15:38:56,004][INFO ][node ] [hades3]
initializing ...
[2014-02-02 15:38:56,027][INFO ][plugins ] [hades3]
loaded [marvel], sites [marvel, head]
[2014-02-02 15:39:01,302][INFO ][node ] [hades3]
initialized
[2014-02-02 15:39:01,302][INFO ][node ] [hades3]
starting ...
[2014-02-02 15:39:01,410][INFO ][transport] [hades3]
bound_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish_address {inet[/
192.168.10.148:9300]}
[2014-02-02 15:39:06,408][ERROR][marvel.agent.exporter] error
sending data
java.io.FileNotFoundException: http://localhost:9200/_bulk
atsun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1623)
at org.elasticsearch.marvel.agent.exporter.ESExporter.
sendCloseExportingConnection(ESExporter.java:232)
at org.elasticsearch.marvel.agent.exporter.ESExporter.
exportXContent(ESExporter.java:252)
at org.elasticsearch.marvel.agent.exporter.ESExporter.
exportNodeStats(ESExporter.java:134)
at org.elasticsearch.marvel.agent.AgentService$ExportingWorker.
exportNodeStats(AgentService.java:274)
at org.elasticsearch.marvel.agent.AgentService$ExportingWorker.
run(AgentService.java:174)
at java.lang.Thread.run(Thread.java:724)
On Sun, Feb 2, 2014 at 3:43 PM, Ron Sher ron.s...@gmail.com wrote:
I've noticed that I didn't have a logging.yml (was called logging.xml
instead).
Changed that and then I see:
[2014-02-02 15:42:19,824][ERROR][marvel.agent.exporter] error
sending data
java.io.FileNotFoundException: http://localhost:9200/_bulk
atsun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1623)
at org.elasticsearch.marvel.agent.exporter.ESExporter.
sendCloseExportingConnection(ESExporter.java:232)
at org.elasticsearch.marvel.agent.exporter.ESExporter.
exportXContent(ESExporter.java:252)
at org.elasticsearch.marvel.agent.exporter.ESExporter.
exportClusterStats(ESExporter.java:172)
at org.elasticsearch.marvel.agent.AgentService$ExportingWorker.
exportClusterStats(AgentService.java:214)
at org.elasticsearch.marvel.agent.AgentService$ExportingWorker.
run(AgentService.java:180)
at java.lang.Thread.run(Thread.java:724)
What now?
On Sun, Feb 2, 2014 at 11:29 AM, Ron Sher ron.s...@gmail.com wrote:
This is what I see in the log after the restart:
STATUS | wrapper | 2014/02/02 11:26:54 | Copyright (C) 1999-2011
Tanuki Software, Ltd. All Rights Reserved.
STATUS | wrapper | 2014/02/02 11:26:54 |
http://wrapper.tanukisoftware.com
STATUS | wrapper | 2014/02/02 11:26:54 |
WARN | wrapper | 2014/02/02 11:26:54 | Encountered an invalid
numerical value for configuration property
wrapper.java.initmemory=%ES_HEAP_SIZE%.
Resolving to 0.
WARN | wrapper | 2014/02/02 11:26:54 | Encountered an invalid
numerical value for configuration property
wrapper.java.maxmemory=%ES_HEAP_SIZE%.
Resolving to 0.
STATUS | wrapper | 2014/02/02 11:26:54 | Launching a JVM...
INFO | jvm 1| 2014/02/02 11:26:55 | WrapperManager:
Initializing...
INFO | jvm 1| 2014/02/02 11:27:01 | log4j:WARN No appenders
could be found for logger (node).
INFO | jvm 1| 2014/02/02 11:27:01 | log4j:WARN Please initialize
the log4j system properly.
INFO | jvm 1| 2014/02/02 11:27:01 | log4j:WARN See
http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
On Sun, Feb 2, 2014 at 10:05 AM, Boaz Leskes b.les...@gmail.comwrote:
OK, interesting.
Can you check the logs on one of the nodes to if there are any errors?
also please double check that when the node started it logged a line
similar to the following (containing marvel in the list after loaded):
[2014-02-02 09:03:48,043][INFO ][plugins ] [
Stonewall] loaded [marvel], sites [marvel]
start a node (one is enough)
On Sunday, February 2, 2014 8:50:47 AM UTC+1,
Re: marvel shows empty dashboard
It looks like you have dynamic mappings disabled - most likely via the
following line in the elasticsearch.yml file:
index.mapper.dynamic: false
You will need to override it for marvel indices which rely on this
functionality. To do so (assuming you don't want to remove that line from
the elasticsearch.yml) add the following index template:
curl -XPUT http://HOST:PORT/_template/custom_marvel; -d'
{
template: .marvel*,
order: 1,
settings: {
mapper.dynamic: true
}
}'
After the template is added, you'd need to delete today's index so it will
be recreated using the new template:
curl -XDELETE http://HOST:PORT/.marvel-2014.02.02;
There is no need to restart nodes. Once the index is re-created the error
should go away (should take ~5 sec)
On Sunday, February 2, 2014 4:38:57 PM UTC+1, Ron Sher wrote:
Getting somewhere...
Changed the hosts and now I get the following:
type[cluster_stats] missing: trying to auto create mapping, but dynamic
mapping is disabled
On Sun, Feb 2, 2014 at 5:26 PM, Boaz Leskes b.le...@gmail.comjavascript:
wrote:
It looks like marvel can't store the data on localhost:9200. The most
common reason is running on another port. Another option is that ES is not
bound on localhost or that http access is turned off (in which case marvel
won't work).
Can you verify you can connect ES via the terminal while on the machine
itself? If needed you can change the host port marvel where sends data
to. See
http://www.elasticsearch.org/guide/en/marvel/current/index.html#stats-export
On Sun, Feb 2, 2014 at 3:23 PM, Ron Sher ron@gmail.com javascript:
wrote:
The beginning of the log looks like:
[2014-02-02 15:38:56,003][INFO ][node ] [hades3]
version[0.90.10], pid[20219], build[0a5781f/2014-01-10T10:18:37Z]
[2014-02-02 15:38:56,004][INFO ][node ] [hades3]
initializing ...
[2014-02-02 15:38:56,027][INFO ][plugins ] [hades3]
loaded [marvel], sites [marvel, head]
[2014-02-02 15:39:01,302][INFO ][node ] [hades3]
initialized
[2014-02-02 15:39:01,302][INFO ][node ] [hades3]
starting ...
[2014-02-02 15:39:01,410][INFO ][transport] [hades3]
bound_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish_address {inet[/
192.168.10.148:9300]}
[2014-02-02 15:39:06,408][ERROR][marvel.agent.exporter] error
sending data
java.io.FileNotFoundException: http://localhost:9200/_bulk
atsun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1623)
at org.elasticsearch.marvel.agent.exporter.ESExporter.
sendCloseExportingConnection(ESExporter.java:232)
at org.elasticsearch.marvel.agent.exporter.ESExporter.
exportXContent(ESExporter.java:252)
at org.elasticsearch.marvel.agent.exporter.ESExporter.
exportNodeStats(ESExporter.java:134)
at org.elasticsearch.marvel.agent.AgentService$ExportingWorker.
exportNodeStats(AgentService.java:274)
at org.elasticsearch.marvel.agent.AgentService$ExportingWorker.
run(AgentService.java:174)
at java.lang.Thread.run(Thread.java:724)
On Sun, Feb 2, 2014 at 3:43 PM, Ron Sher ron@gmail.comjavascript:
wrote:
I've noticed that I didn't have a logging.yml (was called logging.xml
instead).
Changed that and then I see:
[2014-02-02 15:42:19,824][ERROR][marvel.agent.exporter] error
sending data
java.io.FileNotFoundException: http://localhost:9200/_bulk
atsun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1623)
at org.elasticsearch.marvel.agent.exporter.ESExporter.
sendCloseExportingConnection(ESExporter.java:232)
at org.elasticsearch.marvel.agent.exporter.ESExporter.
exportXContent(ESExporter.java:252)
at org.elasticsearch.marvel.agent.exporter.ESExporter.
exportClusterStats(ESExporter.java:172)
at org.elasticsearch.marvel.agent.AgentService$ExportingWorker.
exportClusterStats(AgentService.java:214)
at org.elasticsearch.marvel.agent.AgentService$ExportingWorker.
run(AgentService.java:180)
at java.lang.Thread.run(Thread.java:724)
What now?
On Sun, Feb 2, 2014 at 11:29 AM, Ron Sher ron@gmail.comjavascript:
wrote:
This is what I see in the log after the restart:
STATUS | wrapper | 2014/02/02 11:26:54 | Copyright (C) 1999-2011
Tanuki Software, Ltd. All Rights Reserved.
STATUS | wrapper | 2014/02/02 11:26:54 |
http://wrapper.tanukisoftware.com
STATUS | wrapper | 2014/02/02 11:26:54 |
WARN | wrapper | 2014/02/02 11:26:54 | Encountered an invalid
numerical value for configuration property
wrapper.java.initmemory=%ES_HEAP_SIZE%.
Resolving to 0.
WARN | wrapper | 2014/02/02 11:26:54 | Encountered an invalid
numerical value for configuration property
wrapper.java.maxmemory=%ES_HEAP_SIZE%.
Resolving to 0.
STATUS | wrapper |
Need help with ES Query
Hi,
I'm using an analyzer which includes a standard tokenizer and
lowercase,asciifolding,suggestions_shingle and edgengrams as token filters
in it. The analyzer is same for both indexing and searching. So, for a text
like delhi to goa will be analyzed like:
{
tokens : [ {
token : de,
start_offset : 0,
end_offset : 5,
type : word,
position : 1
}, {
token : del,
start_offset : 0,
end_offset : 5,
type : word,
position : 1
}, {
token : delh,
start_offset : 0,
end_offset : 5,
type : word,
position : 1
}, {
token : delhi,
start_offset : 0,
end_offset : 5,
type : word,
position : 1
}, {
token : de,
start_offset : 0,
end_offset : 8,
type : word,
position : 1
}, {
token : del,
start_offset : 0,
end_offset : 8,
type : word,
position : 1
}, {
token : delh,
start_offset : 0,
end_offset : 8,
type : word,
position : 1
}, {
token : delhi,
start_offset : 0,
end_offset : 8,
type : word,
position : 1
}, {
token : delhi ,
start_offset : 0,
end_offset : 8,
type : word,
position : 1
}, {
token : delhi t,
start_offset : 0,
end_offset : 8,
type : word,
position : 1
}, {
token : delhi to,
start_offset : 0,
end_offset : 8,
type : word,
position : 1
}, {
token : de,
start_offset : 0,
end_offset : 12,
type : word,
position : 1
}, {
token : del,
start_offset : 0,
end_offset : 12,
type : word,
position : 1
}, {
token : delh,
start_offset : 0,
end_offset : 12,
type : word,
position : 1
}, {
token : delhi,
start_offset : 0,
end_offset : 12,
type : word,
position : 1
}, {
token : delhi ,
start_offset : 0,
end_offset : 12,
type : word,
position : 1
}, {
token : delhi t,
start_offset : 0,
end_offset : 12,
type : word,
position : 1
}, {
token : delhi to,
start_offset : 0,
end_offset : 12,
type : word,
position : 1
}, {
token : delhi to ,
start_offset : 0,
end_offset : 12,
type : word,
position : 1
}, {
token : delhi to g,
start_offset : 0,
end_offset : 12,
type : word,
position : 1
}, {
token : delhi to go,
start_offset : 0,
end_offset : 12,
type : word,
position : 1
}, {
token : delhi to goa,
start_offset : 0,
end_offset : 12,
type : word,
position : 1
}, {
token : to,
start_offset : 6,
end_offset : 8,
type : word,
position : 2
}, {
token : to,
start_offset : 6,
end_offset : 12,
type : word,
position : 2
}, {
token : to ,
start_offset : 6,
end_offset : 12,
type : word,
position : 2
}, {
token : to g,
start_offset : 6,
end_offset : 12,
type : word,
position : 2
}, {
token : to go,
start_offset : 6,
end_offset : 12,
type : word,
position : 2
}, {
token : to goa,
start_offset : 6,
end_offset : 12,
type : word,
position : 2
}, {
token : go,
start_offset : 9,
end_offset : 12,
type : word,
position : 3
}, {
token : goa,
start_offset : 9,
end_offset : 12,
type : word,
position : 3
} ]
}
Now, the problem which I'm facing is while querying for delhi t I'm not
getting documents which contains maximum matches for the analyzed tokens of
delhi t on the top:
Instead I get docs which contain only delhi on the top.
I think ES find docs which have maximum match for a certain analyzed search
field which is not happening over here. Can anyone please tell me why is it not
working ? IS there any other query type like match or boolean query which I
need to use ?
Any help will be appreciated.
Thanks
--
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/f5e3eabb-a9de-4d20-9a2e-29bed3c6bed4%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Are the insert operations to elasticsearch asynchronous in nature
If you are using the java API the answer is maybe, it depends on how you use it. In addition, even if you use the synchronous API you have to wait for a refresh for you data to be searchable. By default they happen every second. Sent from my iPhone On Jan 31, 2014, at 6:21 AM, sowjanya sowjanyacha...@gmail.com wrote: I am having a client node and a data node. i am using the client node to communicate to data node. My question is when i perform an insertion from client node does the program control returns to client node once the information is sent to data node over the network or is it blocked till the data is inserted and indexed on the data node. Please help me. -- View this message in context: http://elasticsearch-users.115913.n3.nabble.com/Are-the-insert-operations-to-elasticsearch-asynchronous-in-nature-tp4048555.html Sent from the ElasticSearch Users mailing list archive at Nabble.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/1391167290884-4048555.post%40n3.nabble.com. 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 elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/81D2EDE3-7106-4A8B-A521-B650F8867772%40gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Question on breaking change (boost) in 1.0.0.RC1 release
Thanks much Jörg, this is super helpful. I didn't realize we could wrap a query inside function score query. -Amit. On Fri, Jan 31, 2014 at 1:31 AM, joergpra...@gmail.com joergpra...@gmail.com wrote: See this full example of document boosting with function score query, you can use any query you like. https://gist.github.com/jprante/8728976 Jörg -- 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/CAKdsXoH9FY2xbNGK70Tg9%2B0k75TJmvwkhrcAUuWNDDNkOr%2BGqw%40mail.gmail.com . 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 elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAAOGaQLeSNVQ_1xb1zUJHEYs2koifrOxsRGZXaeO%3DifUZGF8zQ%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Completion - updated inputs are not reflected
Hey nothing, which comes to my mind now. If you manage to reproduce it, please dont hesitate to create a github issue though in order to track it down. Thanks! --Alex On Tue, Jan 28, 2014 at 10:42 AM, barak barak.ya...@gmail.com wrote: The very odd thing is that I just tried running these use cases with the hotels example and it works perfect! So apparently there is no bug on ES side, so I guess I did things wrong. With that in mind, are there some logs I can activate to find out why those docs returned although not matching the inputs?Also tried refresh, optimize, etc. I guess deleting all data and starting all over again will solve it, I just want to find out what I did wrong so I'll try to avoid it in the future... :-) Thanks. On Tuesday, January 28, 2014 10:43:54 AM UTC+2, Alexander Reelsen wrote: Hey, can you post a gist with a full reproduction? See http://www.elasticsearch.org/help I did some tests and the only thing I could come up with, is that if you delete a document, but do not run optimize, you will get old data back. If you index the new document, but you do not refresh after indexing it, you will get back the old result until the next automatic refresh happened. --Alex --Alex On Mon, Jan 27, 2014 at 8:44 PM, barak barak...@gmail.com wrote: So not a clue? I've opened an issue for that on github, but I guess it might takes some time... Any workaround I can use? On Monday, January 27, 2014 4:13:58 PM UTC+2, barak wrote: Did that, still returns the incorrect results. Just to be sure, I even changed the output field, and again - although seen when I examine the doc (head plugin), the api ( REST and JAVA concreteOption.getText().toString() ) returns the old name. Is it possible to delete the data structure directly from the fs? On Monday, January 27, 2014 3:58:08 PM UTC+2, Alexander Reelsen wrote: Hey, can you try running an optimize with expunge deletes set? http://www.elasticsearch.org/guide/en/elasticsearch/referenc e/current/indices-optimize.html curl -XPOST 'http://localhost:9200/twitter/_optimize?only_expunge_ deletes=true' --Alex On Mon, Jan 27, 2014 at 2:22 PM, barak barak...@gmail.com wrote: Hi, I'm using the completion feature on 0.90.9. I've a document which I index with multiple inputs and suggest based search works ok. Then I deleted that doc and re-create it with different inputs, and it still being returned with the first search I did, although I examined the doc (head plugin) and the input field is indeed updated, which does not match that search. Any flush need to issued after updates? Does the suggest API explains the results? Thanks. -- 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. To view this discussion on the web visit https://groups.google.com/d/ msgid/elasticsearch/741ebbf0-2a9d-464c-8946-ca1d13da5ff3%40goo glegroups.com. 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. To view this discussion on the web visit https://groups.google.com/d/ msgid/elasticsearch/13ab2569-038a-4b68-a252-d8ade2c9ca2d% 40googlegroups.com. 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 elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/e107281e-809e-4b9b-bbc2-7c211991d514%40googlegroups.com . 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 elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAGCwEM_M%2BpuvJr08Wjjd5p%2BUXV_Segkkvu324nfdrt74f%2BuGOw%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Some clarity about Update index
Hey,
can you be more specific and provide more information? How do you update a
document without updating the lucene index? Is this some theoretical
eventual consistency fallacy here or something you stumbled across and
should be considered a bug? If so, can you reproduce?
Please be more specific, unsure, what your question is. Thanks!
--Alex
On Wed, Jan 29, 2014 at 4:16 AM, Arjit Gupta arjit...@gmail.com wrote:
Hi ,
Lets say I have a document {name :Jhon} and index is eventually
consistent. I update the document to {name :Tom}.
The lucene index is not updated.
But In search I am getting 1 result for name : Jhon .
1. What will field value for name Jhon or Tom ?
Thanks,
Arjit
--
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/4a3c2b14-ba5b-4def-8aa4-d0a97256c249%40googlegroups.com
.
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 elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAGCwEM8FGxxbWD%2Bc%2BDzvjYfZcCE0jES%3DUWc1vD9K28i4b%3DxztQ%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Persisting IndicesRoutingTable
Hey, there is a specific setting preventing shard allocation, see http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/modules-cluster.html(the disable_allocation setting). Alternatively you can also the gateway recovery to start after a couple of minutes in addition to the expected nodes, which might give you more time to fire up all nodes? --Alex On Wed, Jan 29, 2014 at 4:11 AM, Anantha Govindarajan ananthagovindara...@gmail.com wrote: Hi , In case of planned shutdown (curl -XPOST 'http://localhost:9200/_shutdown') , is it possible to persist the RoutingTable in master node. (In case , we are using separate master and data nodes.) So that when we start the cluster node by node (starting from master) along with gateway.expectednodes setting , then master node can re-use the persisted RoutingTable instead of constructing new one (New one causing unnecessary shard relocation, that too we have shards in big sizes). Once the expected nodes are available in cluster reusing the same avoids unnecessary movement of shrads with-in cluster. Anantha Govindarajan. -- 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/47ce730a-8521-463e-82e8-8eb271548664%40googlegroups.com . 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 elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAGCwEM9r5ukL%2B5gHww%3DeRGrZ7QJEZ0vjMzwNLn2%3D7n0SeoGLWg%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: How to save Query JSON as it is in an Index?
I have an identical requirement and have a question: if we save the query using toXContent() would the same query work fine when the version of elastic search changes (say it went through some major version change)? -Amit. On Wed, Jan 1, 2014 at 12:27 PM, Alexander Reelsen a...@spinscale.de wrote: Hey, you could simply use the toString(), or even better the toXContent() representation of a query and store it in another index, when executing queries using your java API. Alternatively you could set the thresholds for the slow index log very log and thus log every index operation (this has a performance impact), see http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/index-modules-slowlog.html#index-slow-log --Alex On Tue, Dec 31, 2013 at 7:53 PM, Search User feedwo...@gmail.com wrote: I want to save the queries my users are executing and let them re-run at a later time. Thanks, On Tuesday, December 31, 2013 1:21:16 AM UTC-5, Daniel Guo wrote: I don't get your point, can you describe more detail? On Tuesday, December 31, 2013 8:23:22 AM UTC+8, Search User wrote: I want to save the query JSON as it as in a field in an ES index. I should be able to retrieve queries and run it at a later time. I don't need features like percolator. I am using Java client to index and retrieve. What should I do to achieve this? Thanks. -- 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/28ee8010-df47-489f-90df-07e41d831d42%40googlegroups.com . 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 elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAGCwEM8Ua5bLHhhnf5r2VdL99LDQVbazfu%3DsLK1z_w8UHn5W4w%40mail.gmail.com . 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 elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAAOGaQ%2BC5vKe93gFRu1GnHwhH-P2woRP6yutvChWo%3DSFh3rHsw%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
load balance on heterogeneous nodes in a cluster
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 the document and source, I found there is a BalancedShardsAllocator for balancing the shards between nodes with consideration of shards count. But basically, the BalancedShardsAllocator still considers the nodes in the cluster as homogeneous. It seems that we can implement our own ShardsAllocator to distribute shards by predefined machine factor(the simplest way maybe), I want to know whether there is something I missed or there is already some built-in function affording the ability we want? And I also have the related second question, currently our search is not IO-bound because we have big-enough memory on all of our machines but there are different counts of cpu cores in every machine, I want the client search can be distributed to nodes based on the count of cpu cores rather than simple round-robin. Is there any way to do that? -- 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/35708394-19e7-4ab2-ab1a-f632039da26e%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: filtered autocomplete (suggester)
Hey,
the completion suggester does not execute a real search query as it uses
different data structures. This also means, that it does not support
filters. There are plans to support something like a context in order to
have a lightweight filter, see
https://github.com/elasticsearch/elasticsearch/issues/3959
This will allow you suggest only for products in a certain category or for
restaurants around you (as it also has geo support).
--Alex
On Wed, Jan 29, 2014 at 1:18 PM, Ilija Subasic subasic.il...@gmail.comwrote:
Hi,
I am trying to combine it with the query or a filter with suggester, so
that suggestions are returned only for the hits. Is it possible to
constraint autcomplete (or any suggester for that matter) to work on a
subset of data. E.g. I've got some users with associated documents and I
want to serve them document title suggestions but only for the documents
they can access. I've tried:
{
filter : {
term : {
user_id : test
}
},
suggest : {
title_suggester : {
text : r,
completion : {
field : title_suggest
}
}
}
}
and it returns all documents for user test, and all suggestions for all
users. I was able to hack around it by introducing an extra user_id as a
prefix for every suggestions, but looking for a more principled way.
Thanks!
--
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/6589e91d-fcd4-49db-b8c7-317ee800a498%40googlegroups.com
.
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 elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAGCwEM_QnXhauX2MNDX%2BWtqhmBoEypY50om%2BpqrJVi3-QNPJBA%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Missing Indexes After upgrade
Hey, can you start with more logging and check the elasticsearch logfile, if any more suspicious messages occur (maybe including a stacktrace), which might help here? Also, just to verify, eveything runs with correct version, please paste: curl 'localhost:9200/_nodes/jvm?pretty' | grep version --Alex On Wed, Jan 29, 2014 at 10:25 PM, Ryan Shevchik ryan.shevc...@gmail.comwrote: These have both been confirmed. We are running Java 1.7.0_15. On Wed, Jan 29, 2014 at 12:24 PM, Binh Ly b...@hibalo.com wrote: Ryan, Please check and and verify that every single node in your cluster has: 1) Same ES version 2) Same exact Java version (i.e. whatever is displayed when running java -version) -- You received this message because you are subscribed to a topic in the Google Groups elasticsearch group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/elasticsearch/jsJrTjIrUWE/unsubscribe. To unsubscribe from this group and all its topics, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/6b03662c-f982-4b40-8657-274137d31874%40googlegroups.com . 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 elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAAa8yWWN9aUkcDQDd9uaD5XaYo7%2BYxHbjG-ubeeeA%3DOMgB7DRg%40mail.gmail.com . 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 elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAGCwEM9PsA1CuF%3DqAvqcXfnkVZyjF97Pwib8S_0ZyKXYgTbiGw%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
