Re: enabling log compression

[Jason Wee]

there are example here in elasticsearch 1.5?
https://github.com/elastic/elasticsearch/blob/v1.5.0/config/logging.yml#L42-L51

jason

On Tue, May 5, 2015 at 8:13 AM, gleeco  wrote:

> i'm wondering how / if there is support for automatic compression of
> elasticsearch.log via logging.yml.
>
> it looks like there might be via issue #7927
>  and this PR#8464
>  ...but maybe limited
> to v1.5?
>
> ideally, i'd like to see a logging.yml syntax example and clarification of
> what version(s) it works in
>
> thanks in advance!
>
> --
> 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/444d3fba-4780-4a19-af58-4b5b85187925%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAHO4itzS7wB87BuK08hp_w_UiB%3DKXHmhnMmcS%3DdyE%2BQuzuXy%3Dw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Troubleshooting ES Resharding. Nature of immediate tasks and other questions

[Mark Walkom]

The rationale of queuing is to allow for instances where temporary load on
the cluster might otherwise reject a request.
There is no way to prioritise tasks over other tasks.

Though it looks like your problem is you are overloading your nodes. 32192
primary shards is a massive amount for only 12 nodes, you really need to
reduce this pretty dramatically to alleviate the pressure.

On 5 May 2015 at 07:05,  wrote:

> Hi all,
>
> We've been facing some trouble with our Elastic Search installation (v
> 1.5.1), mostly trying
> to bring it back up. Some questions have come up.
>
> This is our situation. We're seeing about 200 unassigned shards, which are
> not being
> reassigned automatically, which in turn leads our ES to move into a red
> status. In this state,
> queries are disabled, however we keep storing data.
>
> What we see is that this generates refresh/update mapping tasks which are
> never resolved (we think
> this is because ES is in a red state). Hoping to solve this, we've been
> running _cluster/reroute on primary
> shards:
>
> curl -XPOST 'localhost:9290/_cluster/reroute' -d '{
>  "commands": [
> {
> "allocate": {
> "index": "'$INDEX'",
> "shard": '$SHARD',
> "node": "'$NODE'",
> "allow_primary": true
>   }
> }
> ]
>   }'
>
> Commands such as _nodes/_local/{stats, settings, os, processes} will fail
> on the master node (hang indefinetly)
>
> We monitor the pending tasks (see _cat/pending_tasks  and _cluster/health
> output below) and see that
> the IMMEDIATE tasks are queued.
>
> However, we're wondering what's the rationale behind the queuing of this
> tasks:
>
> Is there a round robin mechanism for the IMMEDIATE or is there some way of
> prioritizing the
> health state of the cluster over other tasks? Will an IMMEDIATE task
> preempt any other (e.g URGENT or HIGH?)
>
> We've noticed that when queuing two IMMEDIATE tasks, the second one may
> timeout if the first one
> is not resolved fast enough. Is this queue being consumed by a single
> thread? If so, anyway to change that?
>
>
> Thanks in advance!
> Tomás
> ---
>
> _cat/pending_tasks
>   % Total% Received % Xferd  Average Speed   TimeTime Time
>  Current
>  Dload  Upload   Total   SpentLeft
>  Speed
>   0 00 00 0  0  0 --:--:-- --:--:-- --:--:--
>   0220771  2.1m IMMEDIATE cluster_reroute (api)
>
> 220891 29.8s IMMEDIATE cluster_reroute (api)
>
> 196772 10.1h HIGH  update-mapping
> [beer.raw.cl.business.2015-05-04][GDS_search_scans] / node
> [v5SxZ7CdRou13tzy-N1DJg], order [1109]
> 220892 25.9s IMMEDIATE cluster_reroute (api)
>
> 196773 10.1h HIGH  update-mapping
> [beer.raw.pe.business.2015-05-04][GDS_search_scans] / node
> [BTYaSC3cT8K_3xHDQYoNXQ], order [419]
> 196779 10.1h HIGH  update-mapping
> [beer.raw.ar.business.2015-05-04][prism_retrieve] / node
> [iDVZlJycRdeOa1PGB4Oi9Q], order [127]
> 220893 25.7s IMMEDIATE cluster_reroute (api)
>
> 196787 10.1h HIGH  refresh-mapping
> [beer.raw.pt.business.2015-05-03][[GDS_search_scans]]
>
> 196786 10.1h HIGH  refresh-mapping
> [beer.raw.ca.business.2015-05-03][[GDS_search_scans]]
>
> 196774 10.1h HIGH  update-mapping
> [beer.raw.pe.business.2015-05-04][GDS_search_scans] / node
> [Kx-HMg4qQKqepJb1qjjS3A], order [151]
> 196790 10.1h HIGH  refresh-mapping
> [beer.raw.ae.search.2015-05-03][[vito]]
>
> 196792 10.1h HIGH  refresh-mapping
> [beer.raw.tr.business.2015-05-03][[GDS_search_scans]]
>
> 218944 35.5m URGENTshard-started
> ([beer.raw.gy.performance.2015-04-07][2], node[BTYaSC3cT8K_3xHDQYoNXQ],
> relocating [0clH8MU6Q5Wt8phPRbuTLg], [P], s[INITIALIZING]), reason [after
> recovery (replica) from node
> [[beer-elastic-s-08][0clH8MU6Q5Wt8phPRbuTLg][beer-elastic-s-08][inet[/
> 10.70.163.240:9300]]{master=false}]]
>
> 220894 25.7s IMMEDIATE cluster_reroute (api)
>
> 196850 10.1h HIGH  refresh-mapping
> [beer.raw.fi.business.2015-05-03][[GDS_search_scans]]
>
> 196788 10.1h HIGH  refresh-mapping
> [beer.raw.il.business.2015-05-03][[GDS_search_scans]]
>
> 196789 10.1h HIGH  refresh-mapping
> [beer.raw.nl.business.2015-05-03][[GDS_search_scans]]
>
>
>
>
> Health
>
> _cluster/health?pretty=true"
>
>   "cluster_name" : "beer-elastic",
>   "status" : "red",
>   "timed_out" : false,
>   "number_of_nodes" : 20,
>   "number_of_data_nodes" : 12,
>   "active_primary_shards" : 32192,
>   "active_shards" : 64384,
>   "relocating_shards" : 2,
>   "initializing_shards" : 14,
>   "unassigned_shards" : 182,
>   "number_of_pending_tasks" : 13686
>
> --
> 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/e3f4f449-d359-4ef1

Re: Troubleshooting ES Resharding. Nature of immediate tasks and other questions

[Jason Wee]

hello, just out of curiosity, what is the cluster index size and what is
the rationale to have so many shards?

jason

On Tue, May 5, 2015 at 5:05 AM,  wrote:

> Hi all,
>
> We've been facing some trouble with our Elastic Search installation (v
> 1.5.1), mostly trying
> to bring it back up. Some questions have come up.
>
> This is our situation. We're seeing about 200 unassigned shards, which are
> not being
> reassigned automatically, which in turn leads our ES to move into a red
> status. In this state,
> queries are disabled, however we keep storing data.
>
> What we see is that this generates refresh/update mapping tasks which are
> never resolved (we think
> this is because ES is in a red state). Hoping to solve this, we've been
> running _cluster/reroute on primary
> shards:
>
> curl -XPOST 'localhost:9290/_cluster/reroute' -d '{
>  "commands": [
> {
> "allocate": {
> "index": "'$INDEX'",
> "shard": '$SHARD',
> "node": "'$NODE'",
> "allow_primary": true
>   }
> }
> ]
>   }'
>
> Commands such as _nodes/_local/{stats, settings, os, processes} will fail
> on the master node (hang indefinetly)
>
> We monitor the pending tasks (see _cat/pending_tasks  and _cluster/health
> output below) and see that
> the IMMEDIATE tasks are queued.
>
> However, we're wondering what's the rationale behind the queuing of this
> tasks:
>
> Is there a round robin mechanism for the IMMEDIATE or is there some way of
> prioritizing the
> health state of the cluster over other tasks? Will an IMMEDIATE task
> preempt any other (e.g URGENT or HIGH?)
>
> We've noticed that when queuing two IMMEDIATE tasks, the second one may
> timeout if the first one
> is not resolved fast enough. Is this queue being consumed by a single
> thread? If so, anyway to change that?
>
>
> Thanks in advance!
> Tomás
> ---
>
> _cat/pending_tasks
>   % Total% Received % Xferd  Average Speed   TimeTime Time
>  Current
>  Dload  Upload   Total   SpentLeft
>  Speed
>   0 00 00 0  0  0 --:--:-- --:--:-- --:--:--
>   0220771  2.1m IMMEDIATE cluster_reroute (api)
>
> 220891 29.8s IMMEDIATE cluster_reroute (api)
>
> 196772 10.1h HIGH  update-mapping
> [beer.raw.cl.business.2015-05-04][GDS_search_scans] / node
> [v5SxZ7CdRou13tzy-N1DJg], order [1109]
> 220892 25.9s IMMEDIATE cluster_reroute (api)
>
> 196773 10.1h HIGH  update-mapping
> [beer.raw.pe.business.2015-05-04][GDS_search_scans] / node
> [BTYaSC3cT8K_3xHDQYoNXQ], order [419]
> 196779 10.1h HIGH  update-mapping
> [beer.raw.ar.business.2015-05-04][prism_retrieve] / node
> [iDVZlJycRdeOa1PGB4Oi9Q], order [127]
> 220893 25.7s IMMEDIATE cluster_reroute (api)
>
> 196787 10.1h HIGH  refresh-mapping
> [beer.raw.pt.business.2015-05-03][[GDS_search_scans]]
>
> 196786 10.1h HIGH  refresh-mapping
> [beer.raw.ca.business.2015-05-03][[GDS_search_scans]]
>
> 196774 10.1h HIGH  update-mapping
> [beer.raw.pe.business.2015-05-04][GDS_search_scans] / node
> [Kx-HMg4qQKqepJb1qjjS3A], order [151]
> 196790 10.1h HIGH  refresh-mapping
> [beer.raw.ae.search.2015-05-03][[vito]]
>
> 196792 10.1h HIGH  refresh-mapping
> [beer.raw.tr.business.2015-05-03][[GDS_search_scans]]
>
> 218944 35.5m URGENTshard-started
> ([beer.raw.gy.performance.2015-04-07][2], node[BTYaSC3cT8K_3xHDQYoNXQ],
> relocating [0clH8MU6Q5Wt8phPRbuTLg], [P], s[INITIALIZING]), reason [after
> recovery (replica) from node
> [[beer-elastic-s-08][0clH8MU6Q5Wt8phPRbuTLg][beer-elastic-s-08][inet[/
> 10.70.163.240:9300]]{master=false}]]
>
> 220894 25.7s IMMEDIATE cluster_reroute (api)
>
> 196850 10.1h HIGH  refresh-mapping
> [beer.raw.fi.business.2015-05-03][[GDS_search_scans]]
>
> 196788 10.1h HIGH  refresh-mapping
> [beer.raw.il.business.2015-05-03][[GDS_search_scans]]
>
> 196789 10.1h HIGH  refresh-mapping
> [beer.raw.nl.business.2015-05-03][[GDS_search_scans]]
>
>
>
>
> Health
>
> _cluster/health?pretty=true"
>
>   "cluster_name" : "beer-elastic",
>   "status" : "red",
>   "timed_out" : false,
>   "number_of_nodes" : 20,
>   "number_of_data_nodes" : 12,
>   "active_primary_shards" : 32192,
>   "active_shards" : 64384,
>   "relocating_shards" : 2,
>   "initializing_shards" : 14,
>   "unassigned_shards" : 182,
>   "number_of_pending_tasks" : 13686
>
> --
> 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/e3f4f449-d359-4ef1-a6a4-a445bb916371%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You

Re: Kibana, Error editing saved visualization with quotationmark

[Mark Walkom]

You might have to extract the doc from the .kibana index, edit it and then
send it back to get immediate access.

However it'd also be worth raising this as a Github issue, perhaps there is
something that is not being properly escaped under the hood, which causes
the behaviour.

On 4 May 2015 at 20:58,  wrote:

> Hi All,
>
> as we are very new to the ELK stack, I'm not sure if this is the right
> place to ask, but perhaps you can help with the following problem.
>
> We saved some visualization with quotationmark in the name, for example:
> 'Count-exciis_page:-%22-slash-Microsoft-Server-ActiveSync%2Fdefault.eas%22'
>
> Since it was saved, we are not able to change the visualization search
> again. If we select edit on such saved object, it jumps to "Discovery"
> instead of "Visualize".
>
> Is there a way to rename the saved visualization in elasticsearch, so we
> are able to edit it again?
>
> We are using:
> elasticsearch 1.4.4
> kibana 4.0.0 Build 5888
>
> Thanks allot,
> Benedikt
>
> --
> 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/723f4541-d13d-4718-bedc-199b26d25d93%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAEYi1X-qh9C4eb1iCLu3BN_Pvu0pJJQMqYvO1arByDU6Jtg6ZA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

enabling log compression

[gleeco]

i'm wondering how / if there is support for automatic compression of 
elasticsearch.log via logging.yml.

it looks like there might be via issue #7927 
 and this PR#8464 
 ...but maybe limited 
to v1.5?

ideally, i'd like to see a logging.yml syntax example and clarification of 
what version(s) it works in

thanks in advance!

-- 
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/444d3fba-4780-4a19-af58-4b5b85187925%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Forums Are Now Live at http://discuss.elastic.co

[Nikolas Everett]

I think github and pastebins/gists shouldn't be considered against the
limit. We ask people to use gist all the time and github issue or code
links are a good thing to use as well.
On May 4, 2015 5:40 PM, "joergpra...@gmail.com" 
wrote:

> Thanks Shaunak,
>
> I appreciate that. I think it would be more than welcome to let others of
> the community also take the advantage of including Github issues into the
> forum software which contain numerous links:
>
> https://discuss.elastic.co/t/link-level-in-a-post/151
>
> Best,
>
> Jörg
>
>
> On Mon, May 4, 2015 at 11:05 PM,  wrote:
>
>> Hey Jörg,
>>
>> I've removed this restriction from your account. You should be able to
>> post more than 2 links in a post now :)
>>
>> Shaunak
>>
>> On Monday, May 4, 2015 at 2:07:14 PM UTC-5, Jörg Prante wrote:
>>>
>>> It does not work. I can not post messages with links.
>>>
>>> After I try to post a new topic such as
>>>
>>> - snip
>>> To all of you who want to sneak at the features planned for ES 2.0, this
>>> issue collects some of it
>>>
>>> https://github.com/elastic/elasticsearch/issues/9970
>>>
>>> Best,
>>>
>>> Jörg
>>> snip
>>>
>>> I receive a denial
>>>
>>> "Sorry, new users can only put 2 links in a post."
>>>
>>> Beside the fact I included just one link, why this restriction? A bit
>>> sad that I am considered a new user after five years happily using ES but
>>> the machine is always right in the end ;)
>>>
>>> Jörg
>>>
>>>
>>>
>>> On Mon, May 4, 2015 at 6:58 PM, Leslie Hawthorn 
>>> wrote:
>>>


 On Mon, May 4, 2015 at 6:41 PM, Nikolas Everett 
 wrote:

> I suspect its read only while they sort out resourcing issues. Cache
> hit rate is likely quite high while readonly.
> On May 4, 2015 12:38 PM, Jürgen Wagner (DVT) 
> wrote:
>
>> The site is read-only. No signups possible. Hmm...
>>
>
 Our friends at Discourse have reported that the site outage has been
 resolved. They'll keep up with updates via their Twitter account:

 https://twitter.com/discourse/status/595268564493279232

 In the meantime, please go forth and use the forums. If they fall over
 again we will work to ensure speedy resolution.

 Thanks for your patience, folks.

 Cheers,
 LH

 --
 Leslie Hawthorn
 Director of Developer Relations
 http://elastic.co

 Other Places to Find Me:
 Freenode: lh
 Twitter: @lhawthorn




  --
 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/CAHj2c4BDbbSBYHStNuY6wNZ0--JBtqSTQ-7bJoBapzZNfoXUFw%40mail.gmail.com
 
 .

 For more options, visit https://groups.google.com/d/optout.

>>>
>>>  --
>> 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/a0dfa043-430e-4e1f-83e5-69d644651175%40googlegroups.com
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>  --
> 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/CAKdsXoG8smg%3Dy5BsdMxLjEOUE9QW5ZOpDUVBEU%3DnmRXT-bhTPQ%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAPmjWd1a%2B2AbyjLAGcdFM8sMkUwp%3Dy6P_Yw%2B7j1AatBzoh7tpg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Creating and storing ES indices on S3

[Mark Walkom]

It might be possible, but not really recommended as I'd imagine it'd be
pretty slow, which would impact your performance of ES.


On 4 May 2015 at 23:56, Lavesh Gupta  wrote:

> Hi Everyone,
>
> I went through the group and came across various replies by David Pilato,
> Kimchy and other people which stated to use EBS volumes or local disks for
> storing ES indices and S3 for periodic snapshots. Wanted to know the reason
> why using S3 will be a bad choice for creating and storing indices on S3
> (even if I mount S3 to EC2 instance).
>
> My main points for storing and creating indices on S3 are:
>
> 1) I want to avoid cost of using both EBS and S3. (EBS for storing indices
> data and S3 for snapshots). If I only use S3 then due to replication
> feature I do not have to worry about my data loss.
> 2) Using S3 I will not have to worry about failure of nodes as all data is
> in centralized placed being replicated.
> 3) I can use AWS auto scaling feature to much advantage as I can spawn a
> new EC2 machine when demand rises and then all the indexing and querying
> can be done through a central data source on S3.
>
> If somebody can suggest how I can achieve creating and storing of indices
> on S3 it will be a great help.
>
> Thanking You
>
> This message contains confidential information and is intended only for
> the individual to whom it is addressed. If you are not the intended
> recipient, you should not disseminate, distribute or copy this e-mail.
> Please notify the sender immediately by e-mail if you have received this
> e-mail by mistake and permanently delete this e-mail from your system.
> E-mail transmission cannot be guaranteed to be secure or error-free as
> information could be intercepted, corrupted, lost, destroyed, late or
> incomplete, or could contain viruses. The sender therefore does not accept
> liability for any errors or omissions in the contents of this message,
> which arise as a result of e-mail transmission. If verification is
> required, please request a hard-copy version from the sender. Druva,
> www.druva.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/77357d50-d938-4c4b-9a4b-98001e793798%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAEYi1X8UV_%3DEBTLFdvDev4%2BMpVaOUwc7Yw6wBKve3TdO1CnpzQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Dynamically setting discovery.zen.ping.unicast.hosts

[Mark Walkom]

This is not a dynamic setting, it needs to be defined in your config file
and ES needs to be restarted to read it.

On 5 May 2015 at 08:03, Satnam Singh  wrote:

> I would like to dynamically set discovery.zen.ping.multicast.enabled and
> discovery.zen.ping.unicast.hosts -- is this possible?
> I've been looking for a REST API call that I can make from my Go program.
> I have a situation where I can't use multicast (running on GCE) and the 
> cloud-gce
> plug-in  won't work
> for my scenario.
>
> Thank you kindly.
>
> Cheers,
>
> Satnam
>
> --
> 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/96a25263-a767-4bed-9858-a8cbb86b0b78%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAEYi1X8V2KE%2Bw7%3DDHt1f7PHL2%3DOQ8grFPizRKmLNF4CDxJoiwQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Dynamically setting discovery.zen.ping.unicast.hosts

[Satnam Singh]

I would like to dynamically set discovery.zen.ping.multicast.enabled and 
discovery.zen.ping.unicast.hosts -- is this possible?
I've been looking for a REST API call that I can make from my Go program. I 
have a situation where I can't use multicast (running on GCE) and the cloud-gce 
plug-in  won't work for 
my scenario.

Thank you kindly.

Cheers,

Satnam

-- 
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/96a25263-a767-4bed-9858-a8cbb86b0b78%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Forums Are Now Live at http://discuss.elastic.co

[joergpra...@gmail.com]

Thanks Shaunak,

I appreciate that. I think it would be more than welcome to let others of
the community also take the advantage of including Github issues into the
forum software which contain numerous links:

https://discuss.elastic.co/t/link-level-in-a-post/151

Best,

Jörg


On Mon, May 4, 2015 at 11:05 PM,  wrote:

> Hey Jörg,
>
> I've removed this restriction from your account. You should be able to
> post more than 2 links in a post now :)
>
> Shaunak
>
> On Monday, May 4, 2015 at 2:07:14 PM UTC-5, Jörg Prante wrote:
>>
>> It does not work. I can not post messages with links.
>>
>> After I try to post a new topic such as
>>
>> - snip
>> To all of you who want to sneak at the features planned for ES 2.0, this
>> issue collects some of it
>>
>> https://github.com/elastic/elasticsearch/issues/9970
>>
>> Best,
>>
>> Jörg
>> snip
>>
>> I receive a denial
>>
>> "Sorry, new users can only put 2 links in a post."
>>
>> Beside the fact I included just one link, why this restriction? A bit sad
>> that I am considered a new user after five years happily using ES but the
>> machine is always right in the end ;)
>>
>> Jörg
>>
>>
>>
>> On Mon, May 4, 2015 at 6:58 PM, Leslie Hawthorn 
>> wrote:
>>
>>>
>>>
>>> On Mon, May 4, 2015 at 6:41 PM, Nikolas Everett 
>>> wrote:
>>>
 I suspect its read only while they sort out resourcing issues. Cache
 hit rate is likely quite high while readonly.
 On May 4, 2015 12:38 PM, Jürgen Wagner (DVT) 
 wrote:

> The site is read-only. No signups possible. Hmm...
>

>>> Our friends at Discourse have reported that the site outage has been
>>> resolved. They'll keep up with updates via their Twitter account:
>>>
>>> https://twitter.com/discourse/status/595268564493279232
>>>
>>> In the meantime, please go forth and use the forums. If they fall over
>>> again we will work to ensure speedy resolution.
>>>
>>> Thanks for your patience, folks.
>>>
>>> Cheers,
>>> LH
>>>
>>> --
>>> Leslie Hawthorn
>>> Director of Developer Relations
>>> http://elastic.co
>>>
>>> Other Places to Find Me:
>>> Freenode: lh
>>> Twitter: @lhawthorn
>>>
>>>
>>>
>>>
>>>  --
>>> 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/CAHj2c4BDbbSBYHStNuY6wNZ0--JBtqSTQ-7bJoBapzZNfoXUFw%40mail.gmail.com
>>> 
>>> .
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>  --
> 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/a0dfa043-430e-4e1f-83e5-69d644651175%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAKdsXoG8smg%3Dy5BsdMxLjEOUE9QW5ZOpDUVBEU%3DnmRXT-bhTPQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Forums Are Now Live at http://discuss.elastic.co

[shaunak]

Hey Jörg,

I've removed this restriction from your account. You should be able to post 
more than 2 links in a post now :)

Shaunak

On Monday, May 4, 2015 at 2:07:14 PM UTC-5, Jörg Prante wrote:
>
> It does not work. I can not post messages with links.
>
> After I try to post a new topic such as
>
> - snip
> To all of you who want to sneak at the features planned for ES 2.0, this 
> issue collects some of it 
>
> https://github.com/elastic/elasticsearch/issues/9970
>
> Best,
>
> Jörg
> snip
>
> I receive a denial
>
> "Sorry, new users can only put 2 links in a post."
>
> Beside the fact I included just one link, why this restriction? A bit sad 
> that I am considered a new user after five years happily using ES but the 
> machine is always right in the end ;)
>
> Jörg
>
>
>
> On Mon, May 4, 2015 at 6:58 PM, Leslie Hawthorn  > wrote:
>
>>
>>
>> On Mon, May 4, 2015 at 6:41 PM, Nikolas Everett > > wrote:
>>
>>> I suspect its read only while they sort out resourcing issues. Cache hit 
>>> rate is likely quite high while readonly. 
>>> On May 4, 2015 12:38 PM, Jürgen Wagner (DVT) >> > wrote:
>>>
 The site is read-only. No signups possible. Hmm...

>>>
>> Our friends at Discourse have reported that the site outage has been 
>> resolved. They'll keep up with updates via their Twitter account:
>>
>> https://twitter.com/discourse/status/595268564493279232
>>
>> In the meantime, please go forth and use the forums. If they fall over 
>> again we will work to ensure speedy resolution.
>>
>> Thanks for your patience, folks.
>>
>> Cheers,
>> LH 
>>
>> -- 
>> Leslie Hawthorn
>> Director of Developer Relations
>> http://elastic.co
>>
>> Other Places to Find Me:
>> Freenode: lh
>> Twitter: @lhawthorn
>>
>>
>>
>>
>>  -- 
>> 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/CAHj2c4BDbbSBYHStNuY6wNZ0--JBtqSTQ-7bJoBapzZNfoXUFw%40mail.gmail.com
>>  
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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/a0dfa043-430e-4e1f-83e5-69d644651175%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Troubleshooting ES Resharding. Nature of immediate tasks and other questions

[tomas . nino]

Hi all,

We've been facing some trouble with our Elastic Search installation (v 
1.5.1), mostly trying
to bring it back up. Some questions have come up.

This is our situation. We're seeing about 200 unassigned shards, which are 
not being 
reassigned automatically, which in turn leads our ES to move into a red 
status. In this state, 
queries are disabled, however we keep storing data.

What we see is that this generates refresh/update mapping tasks which are 
never resolved (we think
this is because ES is in a red state). Hoping to solve this, we've been 
running _cluster/reroute on primary
shards:

curl -XPOST 'localhost:9290/_cluster/reroute' -d '{
 "commands": [
{
"allocate": {
"index": "'$INDEX'",
"shard": '$SHARD',
"node": "'$NODE'",
"allow_primary": true
  }
}
]
  }'

Commands such as _nodes/_local/{stats, settings, os, processes} will fail 
on the master node (hang indefinetly)

We monitor the pending tasks (see _cat/pending_tasks  and _cluster/health 
output below) and see that
the IMMEDIATE tasks are queued. 

However, we're wondering what's the rationale behind the queuing of this 
tasks:

Is there a round robin mechanism for the IMMEDIATE or is there some way of 
prioritizing the
health state of the cluster over other tasks? Will an IMMEDIATE task 
preempt any other (e.g URGENT or HIGH?)

We've noticed that when queuing two IMMEDIATE tasks, the second one may 
timeout if the first one
is not resolved fast enough. Is this queue being consumed by a single 
thread? If so, anyway to change that? 


Thanks in advance!
Tomás
--- 

_cat/pending_tasks 
  % Total% Received % Xferd  Average Speed   TimeTime Time 
 Current
 Dload  Upload   Total   SpentLeft 
 Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:--   
  0220771  2.1m IMMEDIATE cluster_reroute (api) 
  
220891 29.8s IMMEDIATE cluster_reroute (api)   

196772 10.1h HIGH  update-mapping 
[beer.raw.cl.business.2015-05-04][GDS_search_scans] / node 
[v5SxZ7CdRou13tzy-N1DJg], order [1109] 
220892 25.9s IMMEDIATE cluster_reroute (api)   

196773 10.1h HIGH  update-mapping 
[beer.raw.pe.business.2015-05-04][GDS_search_scans] / node 
[BTYaSC3cT8K_3xHDQYoNXQ], order [419] 
196779 10.1h HIGH  update-mapping 
[beer.raw.ar.business.2015-05-04][prism_retrieve] / node 
[iDVZlJycRdeOa1PGB4Oi9Q], order [127] 
220893 25.7s IMMEDIATE cluster_reroute (api)   

196787 10.1h HIGH  refresh-mapping 
[beer.raw.pt.business.2015-05-03][[GDS_search_scans]]   

196786 10.1h HIGH  refresh-mapping 
[beer.raw.ca.business.2015-05-03][[GDS_search_scans]]   

196774 10.1h HIGH  update-mapping 
[beer.raw.pe.business.2015-05-04][GDS_search_scans] / node 
[Kx-HMg4qQKqepJb1qjjS3A], order [151] 
196790 10.1h HIGH  refresh-mapping 
[beer.raw.ae.search.2015-05-03][[vito]] 

196792 10.1h HIGH  refresh-mapping 
[beer.raw.tr.business.2015-05-03][[GDS_search_scans]]   

218944 35.5m URGENTshard-started 
([beer.raw.gy.performance.2015-04-07][2], node[BTYaSC3cT8K_3xHDQYoNXQ], 
relocating [0clH8MU6Q5Wt8phPRbuTLg], [P], s[INITIALIZING]), reason [after 
recovery (replica) from node 
[[beer-elastic-s-08][0clH8MU6Q5Wt8phPRbuTLg][beer-elastic-s-08][inet[/10.70.163.240:9300]]{master=false}]]
 

220894 25.7s IMMEDIATE cluster_reroute (api)   

196850 10.1h HIGH  refresh-mapping 
[beer.raw.fi.business.2015-05-03][[GDS_search_scans]]   

196788 10.1h HIGH  refresh-mapping 
[beer.raw.il.business.2015-05-03][[GDS_search_scans]]   

196789 10.1h HIGH  refresh-mapping 
[beer.raw.nl.business.2015-05-03][[GDS_search_scans]]   




Health

_cluster/health?pretty=true"

  "cluster_name" : "beer-elastic",
  "status" : "red",
  "timed_out" : false,
  "number_of_nodes" : 20,
  "number_of_data_nodes" : 12,
  "active_primary_shards" : 32192,
  "active_shards" : 64384,
  "relocating_shards" : 2,
  "initializing_shards" : 14,
  "unassigned_shards" : 182,
  "number_of_pending_tasks" : 13686

-- 
You received this message because you are subscribed to the Google Groups 
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails 

Re: Forums Are Now Live at http://discuss.elastic.co

[tyler]

Good feedback Jörg! It really is helpful to figure out which aspects need 
to be tuned so that it fits our needs better. (So, thanks to everyone for 
kicking the tires on it.)

Discourse has *lots* of features that are intended to watch for spammers; 
restricting the number of links in a post is one of them. We worked on the 
settings for these but they can obviously be improved a little. I've raised 
the limit, as posting links to gists/etc. is obviously useful for newcomers 
asking for assistance.

Suggestions to fine-tune the forums is welcome, if you want to make these 
suggestions in the "Meta" category on Discourse, it'll help consolidate 
where we can track all of the feedback (and keep some of the 
Discourse-specific talk on discuss.elastic.co.)

Thanks!

On Monday, May 4, 2015 at 1:07:14 PM UTC-6, Jörg Prante wrote:
>
> It does not work. I can not post messages with links.
>
> After I try to post a new topic such as
>
> - snip
> To all of you who want to sneak at the features planned for ES 2.0, this 
> issue collects some of it 
>
> https://github.com/elastic/elasticsearch/issues/9970
>
> Best,
>
> Jörg
> snip
>
> I receive a denial
>
> "Sorry, new users can only put 2 links in a post."
>
> Beside the fact I included just one link, why this restriction? A bit sad 
> that I am considered a new user after five years happily using ES but the 
> machine is always right in the end ;)
>
> Jörg
>
>
>
> On Mon, May 4, 2015 at 6:58 PM, Leslie Hawthorn  > wrote:
>
>>
>>
>> On Mon, May 4, 2015 at 6:41 PM, Nikolas Everett > > wrote:
>>
>>> I suspect its read only while they sort out resourcing issues. Cache hit 
>>> rate is likely quite high while readonly. 
>>> On May 4, 2015 12:38 PM, Jürgen Wagner (DVT) >> > wrote:
>>>
 The site is read-only. No signups possible. Hmm...

>>>
>> Our friends at Discourse have reported that the site outage has been 
>> resolved. They'll keep up with updates via their Twitter account:
>>
>> https://twitter.com/discourse/status/595268564493279232
>>
>> In the meantime, please go forth and use the forums. If they fall over 
>> again we will work to ensure speedy resolution.
>>
>> Thanks for your patience, folks.
>>
>> Cheers,
>> LH 
>>
>> -- 
>> Leslie Hawthorn
>> Director of Developer Relations
>> http://elastic.co
>>
>> Other Places to Find Me:
>> Freenode: lh
>> Twitter: @lhawthorn
>>
>>
>>
>>
>>  -- 
>> 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/CAHj2c4BDbbSBYHStNuY6wNZ0--JBtqSTQ-7bJoBapzZNfoXUFw%40mail.gmail.com
>>  
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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/f1437e1f-468b-417d-aaa4-ea93c01ff9d7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

no reindexing of NumericFieldValues?

[Valentin]

According to this article 
http://shaierera.blogspot.com/2013/09/boosting-documents-in-lucene.html Lucene 
allows for updating NumericFieldValues without reindexing the whole document. 
The help doc on Partial Updates in Elasticsearch implies otherwise. Can anyone 
explain how it is solved in Elasticsearch? 

-- 
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/232bae36-7bc0-4621-b63b-141710319b0f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

path_hierarchy in my settings / mapping Not Working

[jackiverson22]

Hello,

I'm trying to add taxonomies into my index. I add them like the following 
below.

However, when I do an aggregation as shown below the output breaks up "best 
price" into two separate buckets.
I want "best price" to be only one bucket. What I mean is I don't want my 
taxonomies being broken up by whitespace or any other special characters 
like &, only by /

When I do curl -XGET 
'localhost:9200/_analyze?tokenizer=path_hierarchy&pretty' -d 
'/cars/economy/best price'  then it behaves the way I want it to where 
"best price" is not broken up on whitespace. I'm not sure what is wrong.

Below is my code:


curl -XPUT 'localhost:9200/myindex' -d ' {
"settings":{
  "index": {
 "analysis":{  
"analyzer":{  
"analyzer_taxonomy": {
  "type": "custom",
 "tokenizer": "path_hierarchy"
   }
}
 }
  }
   },
   "mappings":{  
  "myindex":{  
 "properties":{  
"catalog":{  
   "properties":{  
  "price":{  
 "type":"float"
  },
  "name":{  
 "type":"string",
 "index":"not_analyzed"
  },
  "description":{  
 "type":"string"
  },
   "taxonomies":{
 "analyzer":"analyzer_taxonomy",
   "type":"string"
   }
   }
}
 }
  }
   }
}'

curl -XPUT 'localhost:9200/myindex/catalog/1' -d ' {
"name":"corolla",
"price":17999,
"description":"this is a car that is a car that gets you places",
"taxonomies":"/cars/economy"
}'

curl -XPUT 'localhost:9200/myindex/catalog/2' -d ' {
"name":"ferrari",
"price":221500,
"description":"this is a car that is a quick car",
"taxonomies":"/cars/ultimate"
}'

curl -XPUT 'localhost:9200/myindex/catalog/3' -d ' {
"name":"ferrari500",
"price":521500,
"description":"this is a car that is fast car!!!",
"taxonomies":"/cars/ultimate/extreme"
}'

curl -XPUT 'localhost:9200/myindex/catalog/4' -d ' {
"name":"tercel",
"price":2500,
"description":"this is a car that is affordable",
"taxonomies":"/cars/economy/best price"
}'


curl -XPOST 'localhost:9200/myindex/_search?pretty' -d ' {  
   "size":0,
   "aggs":{  
  "stuff":{  
 "terms":{  
"field":"taxonomies"
 }
  }
   }
}'

---
OUTPUT
---
{
  "took" : 1,
  "timed_out" : false,
  "_shards" : {
"total" : 5,
"successful" : 5,
"failed" : 0
  },
  "hits" : {
"total" : 4,
"max_score" : 0.0,
"hits" : [ ]
  },
  "aggregations" : {
"stuff" : {
  "doc_count_error_upper_bound" : 0,
  "sum_other_doc_count" : 0,
  "buckets" : [ {
"key" : "cars",
"doc_count" : 4
  }, {
"key" : "economy",
"doc_count" : 2
  }, {
"key" : "ultimate",
"doc_count" : 2
  }, {
"key" : "best",
"doc_count" : 1
  }, {
"key" : "extreme",
"doc_count" : 1
  }, {
"key" : "price",
"doc_count" : 1
  } ]
}
  }
}


-- 
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/cdd971a8-2225-4335-a63c-309bf45f778b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Forums Are Now Live at http://discuss.elastic.co

[joergpra...@gmail.com]

It does not work. I can not post messages with links.

After I try to post a new topic such as

- snip
To all of you who want to sneak at the features planned for ES 2.0, this
issue collects some of it

https://github.com/elastic/elasticsearch/issues/9970

Best,

Jörg
snip

I receive a denial

"Sorry, new users can only put 2 links in a post."

Beside the fact I included just one link, why this restriction? A bit sad
that I am considered a new user after five years happily using ES but the
machine is always right in the end ;)

Jörg



On Mon, May 4, 2015 at 6:58 PM, Leslie Hawthorn 
wrote:

>
>
> On Mon, May 4, 2015 at 6:41 PM, Nikolas Everett  wrote:
>
>> I suspect its read only while they sort out resourcing issues. Cache hit
>> rate is likely quite high while readonly.
>> On May 4, 2015 12:38 PM, Jürgen Wagner (DVT) 
>> wrote:
>>
>>> The site is read-only. No signups possible. Hmm...
>>>
>>
> Our friends at Discourse have reported that the site outage has been
> resolved. They'll keep up with updates via their Twitter account:
>
> https://twitter.com/discourse/status/595268564493279232
>
> In the meantime, please go forth and use the forums. If they fall over
> again we will work to ensure speedy resolution.
>
> Thanks for your patience, folks.
>
> Cheers,
> LH
>
> --
> Leslie Hawthorn
> Director of Developer Relations
> http://elastic.co
>
> Other Places to Find Me:
> Freenode: lh
> Twitter: @lhawthorn
>
>
>
>
>  --
> 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/CAHj2c4BDbbSBYHStNuY6wNZ0--JBtqSTQ-7bJoBapzZNfoXUFw%40mail.gmail.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAKdsXoGou29NpdVXvToNpxTG-Lp2uDJr_SoQJy_Tfaw4eFi97g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

child value as boosting factor - does this make sense?

[Valentin]

Hi,

I would like to use pageviews to rank our documents. Since pageview-data can 
update daily I just thought it might make sense to put in into a child. Is it 
even possible to boost a parent by using a value of a child? And what happens 
if a child does not exist?

How did you solve this?

Any feedback is very much appreciated!

Regards
Valentin

-- 
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/b625f203-855b-4844-adbe-a17667675c9c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Forums Are Now Live at http://discuss.elastic.co

[Leslie Hawthorn]

On Mon, May 4, 2015 at 6:41 PM, Nikolas Everett  wrote:

> I suspect its read only while they sort out resourcing issues. Cache hit
> rate is likely quite high while readonly.
> On May 4, 2015 12:38 PM, Jürgen Wagner (DVT) 
> wrote:
>
>> The site is read-only. No signups possible. Hmm...
>>
>
Our friends at Discourse have reported that the site outage has been
resolved. They'll keep up with updates via their Twitter account:

https://twitter.com/discourse/status/595268564493279232

In the meantime, please go forth and use the forums. If they fall over
again we will work to ensure speedy resolution.

Thanks for your patience, folks.

Cheers,
LH

-- 
Leslie Hawthorn
Director of Developer Relations
http://elastic.co

Other Places to Find Me:
Freenode: lh
Twitter: @lhawthorn

-- 
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/CAHj2c4BDbbSBYHStNuY6wNZ0--JBtqSTQ-7bJoBapzZNfoXUFw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Forums Are Now Live at http://discuss.elastic.co

[Nikolas Everett]

I suspect its read only while they sort out resourcing issues. Cache hit
rate is likely quite high while readonly.
On May 4, 2015 12:38 PM, Jürgen Wagner (DVT) 
wrote:

> The site is read-only. No signups possible. Hmm...
>
> Good luck!
> --Jürgen
>
> --
> 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/5547A06E.6070902%40devoteam.com
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAPmjWd0qmBxkQ-d63q5CDJqnq1%2B6iPDxS4_0LHw%3DxVsaT%2B0_rQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Forums Are Now Live at http://discuss.elastic.co

[Leslie Hawthorn]

On Mon, May 4, 2015 at 6:38 PM, "Jürgen Wagner (DVT)" <
juergen.wag...@devoteam.com> wrote:

> The site is read-only. No signups possible. Hmm...
>

Known issue - we're addressing. Whee!

We'll update this thread when the issue is resolved.

Cheers,
LH


-- 
Leslie Hawthorn
Director of Developer Relations
http://elastic.co

Other Places to Find Me:
Freenode: lh
Twitter: @lhawthorn

-- 
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/CAHj2c4CKwY4HnW9VVXVaJrF9gkB5Chm9An73OYjJ%3DLwT1nB%3D7g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Forums Are Now Live at http://discuss.elastic.co

[Jürgen Wagner (DVT)]

The site is read-only. No signups possible. Hmm...

Good luck!
--Jürgen

-- 
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/5547A06E.6070902%40devoteam.com.
For more options, visit https://groups.google.com/d/optout.
<>

Re: Forums Are Now Live at http://discuss.elastic.co

[Leslie Hawthorn]

On Mon, May 4, 2015 at 6:21 PM, Nikolas Everett  wrote:

>
>
> On Mon, May 4, 2015 at 12:12 PM, leslie.hawthorn <
> leslie.hawth...@elastic.co> wrote:
>
>> Hello everyone,
>>
>> We took in feedback on moving to a Discourse based forum for about a
>> month, and it sounds like most of the folks who thought it might not be
>> optimal were people who preferred to interact with mailing lists instead of
>> forums.
>>
>> We're pretty confident the email functionality of Discourse will work
>> well for our community, so we've gone ahead and rolled out the forums. You
>> can visit them now and sign up for a user account at
>> http://discuss.elastic.co. Registration is one time only and you can do
>> so with any email address or authorizing via Facebook, GitHub, Google
>> Accounts or Twitter.
>>
>>
> And its falling over. 503s everywhere.
>
> Thanks for the bug report. Addressing now

Cheers,
LH
-- 
Leslie Hawthorn
Director of Developer Relations
http://elastic.co

Other Places to Find Me:
Freenode: lh
Twitter: @lhawthorn
Skype: mebelh
Voice: +31 20 794 7300

-- 
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/CAHj2c4Ci7CE0rUqoBRgKZNLeU02%2BSY4NYSjn_LEYE6cGQfRW-w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Forums Are Now Live at http://discuss.elastic.co

[Nikolas Everett]

On Mon, May 4, 2015 at 12:12 PM, leslie.hawthorn  wrote:

> Hello everyone,
>
> We took in feedback on moving to a Discourse based forum for about a
> month, and it sounds like most of the folks who thought it might not be
> optimal were people who preferred to interact with mailing lists instead of
> forums.
>
> We're pretty confident the email functionality of Discourse will work well
> for our community, so we've gone ahead and rolled out the forums. You can
> visit them now and sign up for a user account at http://discuss.elastic.co.
> Registration is one time only and you can do so with any email address or
> authorizing via Facebook, GitHub, Google Accounts or Twitter.
>
> Once you've created your account, you can set up your preferences to
> receive email as often or as rarely as you would like.
>
> For those who'd prefer to interact solely via email, you can start doing
> so as soon as you've set these preferences. You can find full documentation
> on interacting with the forums solely via email here.[0]
>
> Some anticipated FAQs:
>
> 1) Should I ask for help using the forums on this mailing list?
> You're welcome to ask for help on this list, on IRC (#elasticsearch,
> #logstash or #kibana on Freenode) or within the forum in the Meta Elastic
> category.
>
> 2) Are you going to stop answering questions here?
> No, we're going to leave the mailing list active for at least 30 days so
> our entire community can kick the tires. Quoting our internal company FAQ
> for this very question:
> "If our community members find Discourse to be suboptimal, we may make
> the choice to use the forums only for certain tasks and preserve the
> existing mailing lists."
>
> However, our goal is to provide a single source of truth for information
> on our products, so we're hoping the Discourse based forums really work for
> people. Our employees will be answering your questions with a pointer to a
> forum thread to encourage people to actually interact with the new
> resource, too.
>
> 3) So let's say that the forums work for people. What's the plan?
> We'll set these mailing lists to read-only ~30 days from now (June 1,
> 2015). We're still working with the creators of Discourse to do a full
> import of our mailing list archives, so once that task is complete the
> read-only archives will still be preserved, but you can search through all
> that collective knowledge in one place at http://discuss.elastic.co
>
> 4) Is there an FAQ for using the forums?
> We feel like the user interface for Discourse is pretty intuitive, but we
> have a short Notes on Using This Forum document [1] available to help you
> get started.
>
> 5) Where do I direct praise and pain points for the forums?
> Feedback on the forums should be posted to the Meta Elastic category. [2]
> You can update it via email using address discuss-meta [at] elastic [dot]
> co once you've set up your user account.
>
> 6) I have another question that you have not answered. What should I do?
> Please post a note in the Meta Elastic category, ping in IRC (I'm lh on
> Freenode, though anyone with ChanOps/Voice in #elasticsearch, #logstash and
> #kibana can help) or post a note in this thread.
>
>
> [0] -
> https://discuss.elastic.co/t/email-only-interaction-with-the-forums/106
> [1] - https://discuss.elastic.co/t/notes-on-using-these-forums/118
> [2] - https://discuss.elastic.co/c/meta
>
> Cheers,
> LH
>
> Leslie Hawthorn
> Director of Developer Relations
> http://elastic.co
>
> Other Places to Find Me:
> Freenode: lh
> Twitter: @lhawthorn
>
>
>
And its falling over. 503s everywhere.

-- 
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/CAPmjWd1HbexR-LDr7Y0OipBs5VmaPnOVVJYrGPgwSbnDaFggZA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Forums Are Now Live at http://discuss.elastic.co

[leslie.hawthorn]

Hello everyone,

We took in feedback on moving to a Discourse based forum for about a month, 
and it sounds like most of the folks who thought it might not be optimal 
were people who preferred to interact with mailing lists instead of forums.

We're pretty confident the email functionality of Discourse will work well 
for our community, so we've gone ahead and rolled out the forums. You can 
visit them now and sign up for a user account at http://discuss.elastic.co. 
Registration is one time only and you can do so with any email address or 
authorizing via Facebook, GitHub, Google Accounts or Twitter.

Once you've created your account, you can set up your preferences to 
receive email as often or as rarely as you would like.

For those who'd prefer to interact solely via email, you can start doing so 
as soon as you've set these preferences. You can find full documentation on 
interacting with the forums solely via email here.[0]

Some anticipated FAQs:

1) Should I ask for help using the forums on this mailing list?
You're welcome to ask for help on this list, on IRC (#elasticsearch, 
#logstash or #kibana on Freenode) or within the forum in the Meta Elastic 
category.  

2) Are you going to stop answering questions here?
No, we're going to leave the mailing list active for at least 30 days so 
our entire community can kick the tires. Quoting our internal company FAQ 
for this very question:
"If our community members find Discourse to be suboptimal, we may make the 
choice to use the forums only for certain tasks and preserve the existing 
mailing lists."

However, our goal is to provide a single source of truth for information on 
our products, so we're hoping the Discourse based forums really work for 
people. Our employees will be answering your questions with a pointer to a 
forum thread to encourage people to actually interact with the new 
resource, too.

3) So let's say that the forums work for people. What's the plan?
We'll set these mailing lists to read-only ~30 days from now (June 1, 
2015). We're still working with the creators of Discourse to do a full 
import of our mailing list archives, so once that task is complete the 
read-only archives will still be preserved, but you can search through all 
that collective knowledge in one place at http://discuss.elastic.co 

4) Is there an FAQ for using the forums?
We feel like the user interface for Discourse is pretty intuitive, but we 
have a short Notes on Using This Forum document [1] available to help you 
get started.

5) Where do I direct praise and pain points for the forums?
Feedback on the forums should be posted to the Meta Elastic category. [2] 
You can update it via email using address discuss-meta [at] elastic [dot] 
co once you've set up your user account. 

6) I have another question that you have not answered. What should I do?
Please post a note in the Meta Elastic category, ping in IRC (I'm lh on 
Freenode, though anyone with ChanOps/Voice in #elasticsearch, #logstash and 
#kibana can help) or post a note in this thread.


[0] 
- https://discuss.elastic.co/t/email-only-interaction-with-the-forums/106
[1] - https://discuss.elastic.co/t/notes-on-using-these-forums/118
[2] - https://discuss.elastic.co/c/meta

Cheers,
LH

Leslie Hawthorn
Director of Developer Relations
http://elastic.co

Other Places to Find Me:
Freenode: lh
Twitter: @lhawthorn

-- 
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/1c879411-ee8a-44ac-9e91-54843561baa8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Multi Match Query boosting fields.

[Kirill]

Hi,
My question is related to boosting fields in Multi Match Query.
I have 3 fields: First name, Second name and description. A want the score 
to be low, when it matches description field.
{
  "function_score" : {
"query" : {
  "bool" : {
"must" : [ {
  "multi_match" : {
"query" : "te",
"fields" : [ "description", "name^10", "second_name^20" ],
"type" : "phrase_prefix",
"prefix_length" : 2,
  }
}, {
  "multi_match" : {
"query" : "test",
"fields" : [ "description", "name^10", "second_name^10" ],
"type" : "cross_fields",
"operator" : "AND"
  }
} ]
  }
},
  }
}

 But I mentioned that score doesn't change at all when I change boosting 
 variables(10 or 20). Is there is a way to create smart function, that 
gives low score to objects that matches description field? Thank you in 
advance.

-- 
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/29b352f7-e38a-442b-8653-35e66ced4423%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Evaluating Moving to Discourse - Feedback Wanted

[David Reagan]

>
> Worth thinking through, though I doubt we'll action this any time soon.
> We're doing our best to maintain good coverage in our IRC channels and
> folks would still prefer Elastic employees were around more often. Opening
> up yet another chat mechanism seems like a way to make sure even more
> people feel the same way. ;)
>
Yep, starting something like my suggestion would be a major project. Not
something to do lightly.

One idea, that might be easy to implement, would be to host your own IRC
webchat interface, and if possible, have it automatically open the
elasticsearch channels. Then users could go to elastic.co, hover over the
Community nav link, and just click "chat".


--David Reagan

On Mon, May 4, 2015 at 7:41 AM, Leslie Hawthorn 
wrote:

> Hi David,
>
> On Fri, May 1, 2015 at 8:36 PM, David Reagan  wrote:
>
>> > Why do you find IRC unfriendly? Have you tried using a web based client
>> like irccloud.com?
>> I use webchat.freenode.net.
>>
>> There's a big difference between, "Here's our live chat app." and "Learn
>> how to connect to IRC in order to use live chat." I actively avoided live
>> chat for years simply because I had no interest in learning anything about
>> IRC. For a new user, IRC is not friendly, especially if you are not a
>> developer or are new to it.
>>
>
> I hear you. I think those of us who have been using IRC for decades think
> it is easy. I know I find it more intuitive than HipChat.
>
>>
>> There's also the fact that you are told off if you post any code when
>> asking for help. I could see it if the code sample was really long, but
>> when people get told off when they post three or four lines of code, that's
>> not friendly at all. This has happened to me, and I've seen it happen to
>> others. (Not sure it if was in an ELK channel or not...)
>>
>
> I sure hope not - we pride ourselves on having a courteous and welcoming
> community presence. Each channel has its own culture, and some are brusque
> or downright rude. That's not how we play it. :)
>
>>
>> Plus, figuring out how to start a private conversation, or set your
>> status to away, or registering your username so others can't impersonate
>> you, and so on is not obvious. I still haven't taken the time to figure it
>> out.
>>
>
> Yes, and a pointer to an FAQ doc isn't interesting when you want something
> to just work(TM).
>
>>
>> Ideally, we'd have something that functions similar to HipChat. Nice UI,
>> and code snippets are automatically shortened unless you choose to show the
>> full snippet.
>>
>> Worth thinking through, though I doubt we'll action this any time soon.
> We're doing our best to maintain good coverage in our IRC channels and
> folks would still prefer Elastic employees were around more often. Opening
> up yet another chat mechanism seems like a way to make sure even more
> people feel the same way. ;)
>
> Really appreciate the feedback!
>
> Cheers,
> LH
>
>
>>
>> --David Reagan
>>
>> On Fri, May 1, 2015 at 11:17 AM, Leslie Hawthorn <
>> leslie.hawth...@elastic.co> wrote:
>>
>>>
>>>
>>> On Fri, May 1, 2015 at 7:26 PM, David Reagan  wrote:
>>>
 Moving away from mailing lists for anything except announcements would
 be awesome. Forums are a much better way to have solid discussions with
 multiple people in. Email is fine, but when you add in more than a couple
 people, it gets confusing fast. Forums are also far more user friendly for
 people who haven't learned the various ways developers communicate.

 Thanks for your feedback!
>>>
>>>
 That said, if the forum idea is scrapped, please be sure to stick with
 Google Groups or something similar. Don't switch to something like the
 Debian user lists. Every time a search result pops up from a list like that
 when I am looking for help, I can never figure out if I've seen all the
 emails in the thread or not. The interface is just horrid. Google Groups at
 least has conversation view.

>>>
>>> Mailman is little painful, but with the latest release it's become a bit
>>> friendlier.
>>>

 On a similar subject, is there any chance we could get a real time chat
 app that is more user friendly than IRC? Does something exist that could
 sit on top of IRC and alleviate the IRC's user unfriendliness?

>>>
>>> Why do you find IRC unfriendly? Have you tried using a web based client
>>> like irccloud.com?
>>>
>>> Cheers,
>>> LH
>>>


 On Thursday, April 2, 2015 at 8:36:33 AM UTC-7, leslie.hawthorn wrote:
>
> Hello everyone,
>
> As we’ve begun to scale up development on three different open source
> projects, we’ve found Google Groups to be a difficult solution for dealing
> with all of our needs for community support. We’ve got multiple mailing
> lists going, which can be confusing for new folks trying to figure out
> where to go to ask a question.
>
> We’ve also found our lists are becoming noisy in the “good problem to
> have” ki

Re: Evaluating Moving to Discourse - Feedback Wanted

[Leslie Hawthorn]

Hi David,

On Fri, May 1, 2015 at 8:36 PM, David Reagan  wrote:

> > Why do you find IRC unfriendly? Have you tried using a web based client
> like irccloud.com?
> I use webchat.freenode.net.
>
> There's a big difference between, "Here's our live chat app." and "Learn
> how to connect to IRC in order to use live chat." I actively avoided live
> chat for years simply because I had no interest in learning anything about
> IRC. For a new user, IRC is not friendly, especially if you are not a
> developer or are new to it.
>

I hear you. I think those of us who have been using IRC for decades think
it is easy. I know I find it more intuitive than HipChat.

>
> There's also the fact that you are told off if you post any code when
> asking for help. I could see it if the code sample was really long, but
> when people get told off when they post three or four lines of code, that's
> not friendly at all. This has happened to me, and I've seen it happen to
> others. (Not sure it if was in an ELK channel or not...)
>

I sure hope not - we pride ourselves on having a courteous and welcoming
community presence. Each channel has its own culture, and some are brusque
or downright rude. That's not how we play it. :)

>
> Plus, figuring out how to start a private conversation, or set your status
> to away, or registering your username so others can't impersonate you, and
> so on is not obvious. I still haven't taken the time to figure it out.
>

Yes, and a pointer to an FAQ doc isn't interesting when you want something
to just work(TM).

>
> Ideally, we'd have something that functions similar to HipChat. Nice UI,
> and code snippets are automatically shortened unless you choose to show the
> full snippet.
>
> Worth thinking through, though I doubt we'll action this any time soon.
We're doing our best to maintain good coverage in our IRC channels and
folks would still prefer Elastic employees were around more often. Opening
up yet another chat mechanism seems like a way to make sure even more
people feel the same way. ;)

Really appreciate the feedback!

Cheers,
LH


>
> --David Reagan
>
> On Fri, May 1, 2015 at 11:17 AM, Leslie Hawthorn <
> leslie.hawth...@elastic.co> wrote:
>
>>
>>
>> On Fri, May 1, 2015 at 7:26 PM, David Reagan  wrote:
>>
>>> Moving away from mailing lists for anything except announcements would
>>> be awesome. Forums are a much better way to have solid discussions with
>>> multiple people in. Email is fine, but when you add in more than a couple
>>> people, it gets confusing fast. Forums are also far more user friendly for
>>> people who haven't learned the various ways developers communicate.
>>>
>>> Thanks for your feedback!
>>
>>
>>> That said, if the forum idea is scrapped, please be sure to stick with
>>> Google Groups or something similar. Don't switch to something like the
>>> Debian user lists. Every time a search result pops up from a list like that
>>> when I am looking for help, I can never figure out if I've seen all the
>>> emails in the thread or not. The interface is just horrid. Google Groups at
>>> least has conversation view.
>>>
>>
>> Mailman is little painful, but with the latest release it's become a bit
>> friendlier.
>>
>>>
>>> On a similar subject, is there any chance we could get a real time chat
>>> app that is more user friendly than IRC? Does something exist that could
>>> sit on top of IRC and alleviate the IRC's user unfriendliness?
>>>
>>
>> Why do you find IRC unfriendly? Have you tried using a web based client
>> like irccloud.com?
>>
>> Cheers,
>> LH
>>
>>>
>>>
>>> On Thursday, April 2, 2015 at 8:36:33 AM UTC-7, leslie.hawthorn wrote:

 Hello everyone,

 As we’ve begun to scale up development on three different open source
 projects, we’ve found Google Groups to be a difficult solution for dealing
 with all of our needs for community support. We’ve got multiple mailing
 lists going, which can be confusing for new folks trying to figure out
 where to go to ask a question.

 We’ve also found our lists are becoming noisy in the “good problem to
 have” kind of way. As we’ve seen more user adoption, and across such a wide
 variety of use cases, we’re getting widely different types of questions
 asked. For example, I can imagine that folks not using our Python client
 would rather not be distracted with emails about it.

 There’s also a few other strikes against Groups as a tool, such as the
 fact that it is no longer a supported product by Google, it provides no API
 hooks and it is not available for users in China.

 We’ve evaluated several options and we’re currently considering
 shuttering the elasticsearch-user and logstash-users Google Groups in favor
 of a Discourse forum. You can read more about Discourse at
 http://www.discourse.org

 We feel Discourse will allow us to provide a better experience for all
 of our users for a few reasons:

 * More fine graine

Debugging and optimising queries and indicies

[Кирилл Ширинкин]

I have a small set of data ~120Gb collected over 7 days and Kibana 
dashboard with 4 widgets. All fields of indices are not analysed (I've 
turned it off because for this data splitting strings into terms is not 
needed). When I open the dashboard it takes ElasticSearch *minutes* to 
process request and then it just throws Timeout. Timeout is fine if request 
takes too long, but the problem is *why does it take so long*? I know that 
it depends on data, on type of visualisations I've used etc. etc. So the 
more valid question is: *how do I debug this request, and how do I optimise 
them and/or indices to be faster?* I would like to get search results 
within few seconds. What is an advised workflow for improving performance 
in ES?

-- 
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/bcddff75-fd6b-43bd-8325-b21de1cf43c6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: ElasticSearch built-in Jackson stream parser is fastest way to extract fields

[Swati Jain]

Thanks Brian for your reply. I have started using the jars that you 
suggested here and they are easy to work with. Thank you.

Swati

On Thursday, April 30, 2015 at 5:47:43 PM UTC-4, Brian wrote:
>
> Swati,
>
> Well, I tend not to use the built-in Jackson parser anymore. The only 
> advantage I've seen to stream parsing is that I can dynamically adapt to 
> different objects in my own code. But I can't release the code since it's 
> owned by my employer. And for most tasks these days, I use the Jackson jar 
> files and the data binding model. By the way, here are the only additional 
> JAR files that I use in my Elasticsearch-based tools that also include 
> Elasticsearch jars:
>
> For the full Jackson support. There are later versions but these work for 
> now until the rest of the company moves to Java 8:
>
> jackson-annotations-2.2.3.jar
> jackson-core-2.2.3.jar
> jackson-databind-2.2.3.jar
>
> This gives me the full Netty server (got tired of looking for it buried 
> inside ES, and found this to be very simple and easy to use). Again, there 
> are later versions but this one works well enough:
>
> netty-3.5.8.Final.jar
>
> And this is the magic that brings Netty to life. My front end simply 
> publishes each incoming Netty MessageEvent to the LMAX Disruptor ring 
> buffer. Then I can predefine a fixed number of background WorkHandler 
> threads to consume the MessageEvent objects, handling each one and 
> responding back to its client. No matter how much load is slammed into the 
> front end, the number of Netty threads stays small since they only publish 
> and they're done. And so, the total thread count stays small even when 
> intense bursts of clients slam the server:
>
> disruptor-3.2.0.jar
>
> I hope this helps. I'd love to publish more details but this is about all 
> I can do for now.
>
> 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 elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/32783ea6-faaf-4a77-9dfa-31be451939c1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Creating and storing ES indices on S3

[Lavesh Gupta]

Hi Everyone,

I went through the group and came across various replies by David Pilato, 
Kimchy and other people which stated to use EBS volumes or local disks for 
storing ES indices and S3 for periodic snapshots. Wanted to know the reason 
why using S3 will be a bad choice for creating and storing indices on S3 
(even if I mount S3 to EC2 instance).

My main points for storing and creating indices on S3 are:

1) I want to avoid cost of using both EBS and S3. (EBS for storing indices 
data and S3 for snapshots). If I only use S3 then due to replication 
feature I do not have to worry about my data loss.
2) Using S3 I will not have to worry about failure of nodes as all data is 
in centralized placed being replicated.
3) I can use AWS auto scaling feature to much advantage as I can spawn a 
new EC2 machine when demand rises and then all the indexing and querying 
can be done through a central data source on S3. 

If somebody can suggest how I can achieve creating and storing of indices 
on S3 it will be a great help.

Thanking You

-- 


This message contains confidential information and is intended only for the 
individual to whom it is addressed. If you are not the intended recipient, 
you should not disseminate, distribute or copy this e-mail. Please notify 
the sender immediately by e-mail if you have received this e-mail by 
mistake and permanently delete this e-mail from your system. E-mail 
transmission cannot be guaranteed to be secure or error-free as information 
could be intercepted, corrupted, lost, destroyed, late or incomplete, or 
could contain viruses. The sender therefore does not accept liability for 
any errors or omissions in the contents of this message, which arise as a 
result of e-mail transmission. If verification is required, please request 
a hard-copy version from the sender. Druva, www.druva.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/77357d50-d938-4c4b-9a4b-98001e793798%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Why elasticsearch defined default analyzer doesn't work?

[Lin Zhu]

I put content in elasticsearch without define the index setting. It seems 
by default elasticsearch isn't using the default analyzer I defined in 
elasticsearch.yml.

 index.analysis.analyzer.default.type: ik


If I request: http://localhost:9200/useridx/_search?q=Lin

it doesn't using the default analyzer

*Could some one help me make the default analyzer ik when querying?*

-- 
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/7ab51e8c-cd1c-447e-8f1c-cd17d9f76e38%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Kibana TimeZone queries

[phani . nadiminti]

Hi All,

   when I used Kibana 4 I found some interesting scenarios please find the 
following image I include my queries there and help me in this.



Thanks
phani

-- 
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/8d4c7733-4529-4cf7-a87a-83d92bd93742%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: ES upgrade

[Mark Walkom]

I'd try disabling your firewall and eliminating it as a problem, checking
if the nodes can reach each other, and then going from there.


On 4 May 2015 at 20:23,  wrote:

> mark I opened that port already even though I am getting that warning...
>
>  [2015-05-04 01:32:23,947][WARN ][transport.netty  ] [ES_Node11]
> exception caught on transport layer [[id: 0x966e38f5, /10.0.0.249:4485 =>
> /10.0.0.43:9300]], closing connection
>
>is there any problem with this port showing in above warning
> 10.0.0.249:4485.?
>
>
>
>
> On Friday, May 1, 2015 at 4:51:45 PM UTC+5:30, phani.n...@goktree.com
> wrote:
>>
>> Hi All
>>
>>i upgraded elastic search from 1.4.2 to  1.5.2 i am getting following
>> warning from console after upgrade please explain me the following error
>> why it is coming.
>>
>> [2015-05-01 06:15:13,361][WARN ][transport.netty  ] [ES_Node1]
>> exception caught on transport layer [[id: 0xc483723b, /:3845 =>
>> /:9300]], closing connection
>> java.io.StreamCorruptedException: invalid internal transport message
>> format, got (47,45,54,20)
>> at
>> org.elasticsearch.transport.netty.SizeHeaderFrameDecoder.decode(SizeHeaderFrameDecoder.java:47)
>> at
>> org.elasticsearch.common.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:425)
>> at
>> org.elasticsearch.common.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:303)
>> at
>> org.elasticsearch.common.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70)
>> at
>> org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)
>> at
>> org.elasticsearch.common.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791)
>> at
>> org.elasticsearch.common.netty.OpenChannelsHandler.handleUpstream(OpenChannelsHandler.java:74)
>> at
>> org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)
>> at
>> org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:559)
>> at
>> org.elasticsearch.common.netty.channel.Channels.fireMessageReceived(Channels.java:268)
>> at
>> org.elasticsearch.common.netty.channel.Channels.fireMessageReceived(Channels.java:255)
>> at
>> org.elasticsearch.common.netty.channel.socket.nio.NioWorker.read(NioWorker.java:88)
>> at
>> org.elasticsearch.common.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:108)
>> at
>> org.elasticsearch.common.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:337)
>> at
>> org.elasticsearch.common.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:89)
>> at
>> org.elasticsearch.common.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178)
>> at
>> org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
>> at
>> org.elasticsearch.common.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
>> at
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>>
>>
>> Thanks
>> phani
>>
>>  --
> 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/5c965276-4c0c-4c20-a85f-6918518fa912%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAEYi1X9tfp1ev308x4ZAEFi%2BbL0D%2BpbjnpkKW6qYsRaV-GmNog%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Kibana, Error editing saved visualization with quotationmark

[sundbing]

Hi All,

as we are very new to the ELK stack, I'm not sure if this is the right 
place to ask, but perhaps you can help with the following problem.

We saved some visualization with quotationmark in the name, for example:
'Count-exciis_page:-%22-slash-Microsoft-Server-ActiveSync%2Fdefault.eas%22'

Since it was saved, we are not able to change the visualization search 
again. If we select edit on such saved object, it jumps to "Discovery" 
instead of "Visualize".

Is there a way to rename the saved visualization in elasticsearch, so we 
are able to edit it again?

We are using:
elasticsearch 1.4.4
kibana 4.0.0 Build 5888

Thanks allot,
Benedikt

-- 
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/723f4541-d13d-4718-bedc-199b26d25d93%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Memory usage of the machine with ES is continuously increasing

[Pradeep Reddy]

ES version 1.5.2
Arch Linux on Amazon EC2
of the available 16 GB, 8 GB is heap (mlocked). Memory consumption is 
continuously increasing (225 MB per day). 
Total no of documents is around 800k, 500 MB. 

cat /proc/meminfo has 
>
> Slab: 3424728 kB 

SReclaimable: 3407256 kB
>

 

curl -XGET 'http://localhost:9200/_nodes/stats/jvm?pretty' 
>
> "heap_used_in_bytes" : 5788779888,
>   "heap_used_percent" : 67,
>   "heap_committed_in_bytes" : 8555069440,
>
>
slabtop
 OBJS ACTIVE  USE OBJ SIZE  SLABS OBJ/SLAB CACHE SIZE 
NAME   
17750313 17750313 100%0.19K 845253   21   3381012K dentry
 

So the continuous increase in memory usage is because of the slab usage I 
think, If I restart ES, then slab memory is freed. I see that ES still has 
some free heap available, but from elastic documentation  

> Lucene is designed to leverage the underlying OS for caching in-memory 
> data structures. Lucene segments are stored in individual files. Because 
> segments are immutable, these files never change. This makes them very 
> cache friendly, and the underlying OS will happily keep hot segments 
> resident in memory for faster access.
>

My question is, should I add more nodes or increase the ram of each node to 
let lucene use as much memory as it wants ? how significant performance 
difference will be there if I choose to upgrade ES machines to have more 
RAM. 

Or, can I make some optimizations that decreases the slab usage or clean 
slab memory partially?


-- 
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/5ccc7887-59f8-4267-ac05-450f00c42045%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to define the analyzer when creating index?

[Lin Zhu]

At search time, the  

 
sequence
 
is slightly different:

   - *The analyzer defined in the query itself, else*
   - The analyzer defined in the field mapping, else
   - The default analyzer for the type, which defaults to
   - The analyzer named default in the index settings, which defaults to
   - The analyzer named default at node level, which defaults to
   - The standard analyzer

I notice this, but I haven't define analyzer in field mapping, or for some 
type and index.


在 2015年5月4日星期一 UTC+8下午6:27:06，Lin Zhu写道：
>
> How to define a analyzer for an index, not just field?
>
>
> It seems by default it will not using the default analyzer I defined in 
> elasticsearch.yml.
> index.analysis.analyzer.default.type: ik
>
> If I request: 
> http://localhost:9200/useridx/_search?q=Lin it doesn't using the default 
> analyzer.
>
> And this works:
> http://localhost:9200/useridx/_search?analyzer=ik&q=Lin
>
> Do we need each query time set the analyzer?
>

-- 
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/e184e670-e8e9-42f8-afc0-092c8363e9b6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Difference between Delete All indices and Close All indices

[Mark Walkom]

Close leaves them on disk but removes them from being queried, which also
means it takes barely any heap to maintain.
It might be useful if you have lots of disk space but not much heap, it
just means you have to manually open them when you want to query them.

On 4 May 2015 at 20:01, Rubén Ortiz  wrote:

> Hi
>
> I'm learning how to maintain clean my ES and I found this article today
>
>
> http://www.elastic.co/guide/en/elasticsearch/client/curator/current/examples.html
>
> The first example is "Delete all indices older than". I've installed
> curator tool to execute the command:
>
> *# curator delete indices --older-than 14 --time-unit days --timestring
> '%Y.%m.%d'*
> 2015-05-04 11:50:49,600 INFO  Job starting: delete indices
> 2015-05-04 11:50:49,613 INFO  Pruning Kibana-related indices to
> prevent accidental deletion.
> 2015-05-04 11:50:50,046 INFO  Job completed successfully.
>
> then I've checked again my index and the index called
> "logstash-2015.04.19" have disappeared. So, turns out it really remove all
> index and the documents but then... What is difference with "close indices"?
>
> 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/01b265a5-e482-44ce-b0e6-6489f1ad4e1d%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAEYi1X-2DNU4FUbj_PPLy-4h%3DrLVi%3DJcK-WDBLTZmOzumYdLcA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

How to define the analyzer when creating index?

[Lin Zhu]

How to define a analyzer for an index, not just field?


It seems by default it will not using the default analyzer I defined in 
elasticsearch.yml.
index.analysis.analyzer.default.type: ik

If I request: 
http://localhost:9200/useridx/_search?q=Lin it doesn't using the default 
analyzer.

And this works:
http://localhost:9200/useridx/_search?analyzer=ik&q=Lin

Do we need each query time set the analyzer?

-- 
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/7b6c3368-d8b4-4178-9a55-d49a0461b1c3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: ES upgrade

[phani . nadiminti]

mark I opened that port already even though I am getting that warning...

 [2015-05-04 01:32:23,947][WARN ][transport.netty  ] [ES_Node11] 
exception caught on transport layer [[id: 0x966e38f5, /10.0.0.249:4485 => 
/10.0.0.43:9300]], closing connection

   is there any problem with this port showing in above warning 
10.0.0.249:4485.?

   
  

On Friday, May 1, 2015 at 4:51:45 PM UTC+5:30, phani.n...@goktree.com wrote:
>
> Hi All
>
>i upgraded elastic search from 1.4.2 to  1.5.2 i am getting following 
> warning from console after upgrade please explain me the following error 
> why it is coming.
>
> [2015-05-01 06:15:13,361][WARN ][transport.netty  ] [ES_Node1] 
> exception caught on transport layer [[id: 0xc483723b, /:3845 => 
> /:9300]], closing connection
> java.io.StreamCorruptedException: invalid internal transport message 
> format, got (47,45,54,20)
> at 
> org.elasticsearch.transport.netty.SizeHeaderFrameDecoder.decode(SizeHeaderFrameDecoder.java:47)
> at 
> org.elasticsearch.common.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:425)
> at 
> org.elasticsearch.common.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:303)
> at 
> org.elasticsearch.common.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70)
> at 
> org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)
> at 
> org.elasticsearch.common.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791)
> at 
> org.elasticsearch.common.netty.OpenChannelsHandler.handleUpstream(OpenChannelsHandler.java:74)
> at 
> org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)
> at 
> org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:559)
> at 
> org.elasticsearch.common.netty.channel.Channels.fireMessageReceived(Channels.java:268)
> at 
> org.elasticsearch.common.netty.channel.Channels.fireMessageReceived(Channels.java:255)
> at 
> org.elasticsearch.common.netty.channel.socket.nio.NioWorker.read(NioWorker.java:88)
> at 
> org.elasticsearch.common.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:108)
> at 
> org.elasticsearch.common.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:337)
> at 
> org.elasticsearch.common.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:89)
> at 
> org.elasticsearch.common.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178)
> at 
> org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
> at 
> org.elasticsearch.common.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>
>
> Thanks
> phani
>
>

-- 
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/5c965276-4c0c-4c20-a85f-6918518fa912%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Difference between Delete All indices and Close All indices

[Rubén Ortiz]

Hi

I'm learning how to maintain clean my ES and I found this article today

http://www.elastic.co/guide/en/elasticsearch/client/curator/current/examples.html

The first example is "Delete all indices older than". I've installed 
curator tool to execute the command:

*# curator delete indices --older-than 14 --time-unit days --timestring 
'%Y.%m.%d'*
2015-05-04 11:50:49,600 INFO  Job starting: delete indices
2015-05-04 11:50:49,613 INFO  Pruning Kibana-related indices to prevent 
accidental deletion.
2015-05-04 11:50:50,046 INFO  Job completed successfully.

then I've checked again my index and the index called "logstash-2015.04.19" 
have disappeared. So, turns out it really remove all index and the 
documents but then... What is difference with "close indices"?

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/01b265a5-e482-44ce-b0e6-6489f1ad4e1d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Requirejs with Elasticsearch Angular app throwing "lib/connectors/angular" has not been loaded yet for context: _. Use require([])

[Nithyanand]

I am trying to build Elasticsearch Angular app. I am using require.js.

main.js

require.config({

paths : {
'angular' : '../bower_components/angular/angular',
'elasticsearch' : '../node_modules/elasticsearch/src/elasticsearch.angular',
'app' : 'app',
'coreModule':'coreModule',
'esClient' : 'service/esClient'
},

shim : {

'app':{
'deps' : ['angular','coreModule']
},

'coreModule' : {
'deps' :['angular', 'elasticsearch','esClient']   
},

'esClient' : {
'deps' :['angular', 'elasticsearch']   
}

}

});

require(['app'], function(){

angular.bootstrap(document, ['app']); 
});

esClient.js

define(function(){

var esClient=angular.module('esClient', ['elasticsearch']);

esClient.service('client', function (esFactory) {
return esFactory({
host: 'http://localhost:9200',
apiVersion: '1.5',
log: 'trace'
});
});

});

--

But it is throwing the following errors. Anyone else faced this issue?

Uncaught Error: Module name "lib/connectors/angular" has not been loaded 
yet for context: _. Use require([])
http://requirejs.org/docs/errors.html#notloaded
makeError @ require.js:166
localRequire @ require.js:1407
requirejs @ require.js:1752
(anonymous function) @ elasticsearch.angular.js:7
coreModule.js:3 coreModule module
app.js:4 App module
angular.js:63 Uncaught Error: [$injector:modulerr] Failed to instantiate 
module app due to:
Error: [$injector:modulerr] Failed to instantiate module coreModule due to:
Error: [$injector:modulerr] Failed to instantiate module esClient due to:
Error: [$injector:modulerr] Failed to instantiate module elasticsearch due 
to:
Error: [$injector:nomod] Module 'elasticsearch' is not available! You 
either misspelled the module name or forgot to load it. If registering a 
module ensure that you specify the dependencies as the second argument.

PS : I previous used bower installed elasticsearch. Now using npm install. 
Hence the updated comment.

-- 
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/7446c914-3e4c-4183-8399-cc72d436b8b7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: About replica shard use many field data

[Junheng Gong]

Thanks for you replay Mark,

"active": {
 "primaries": {
"fielddata": {
   "memory_size_in_bytes": 77076457764,
   "evictions": 0,
   "fields": {
  "commentsCount": {
 "memory_size_in_bytes": 2416090508
  },
  "_uid": {
 "memory_size_in_bytes": 46517210860
  },
  "sourceTimeUnit": {
 "memory_size_in_bytes": 4160954108
  },
  "likesCount": {
 "memory_size_in_bytes": 4225460468
  },
  "imageCount": {
 "memory_size_in_bytes": 435807840
  },
  "geo": {
 "memory_size_in_bytes": 19320933980
  }
   }
}
 },
 "total": {
"fielddata": {
   "memory_size_in_bytes": 90893341516,
   "evictions": 0,
   "fields": {
  "commentsCount": {
 "memory_size_in_bytes": 2661775356
  },
  "_uid": {
 "memory_size_in_bytes": 55220225456
  },
  "sourceTimeUnit": {
 "memory_size_in_bytes": 4846336504
  },
  "likesCount": {
 "memory_size_in_bytes": 4712145912
  },
  "imageCount": {
 "memory_size_in_bytes": 517060176
  },
  "geo": {
 "memory_size_in_bytes": 22935798112
  }
   }
}
 }
  },

we got field data usage by using GET /_stats/fielddata?fields=*

in this result total is more than primaries, so i thought maybe some 
replica load data to field data too. (cause some query will send to replica 
shard)

在 2015年5月4日星期一 UTC+8下午4:50:38，Junheng Gong写道：
>
> we have about 2.2B data in our elasticsearch, and we using facet and 
> function score query on those data. 
>
> it will load many data to fielddata, and replica double it.
>
> so my question is "how to set replica to make sure it won't use field data 
> expect primary shard down"?
>

-- 
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/8928f963-47c9-478f-acbb-5b594cd4a9ff%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Elasticsearch crashing, Dashboards missing

[Mark Walkom]

Kibana dashboards are saved in kibana-int for KB 3 and .kibana for KB4.

It looks like you are running out of heap, ie an OOM. How much memory have
you assigned to ES and can you increase that?

On 4 May 2015 at 18:12, xiro86  wrote:

> Hi,
>
> I've set up ELK-Stack for Monitoring of our Firewall logging. It works
> fine, we have two dashboards rotating on a screen and are very happy with
> it. Unfortunately it crashed now already for the second time with the same
> error. This won't be that dramatic, since it works after a restart of the
> services - but the critical thing about it is, that the saved dashboards
> disappear also.
>
> Since I can't figure out where the dashboards are saved, I can't even do a
> backup of them.
>
> Is it even possible to backup the dashboard only - and where is it stored?
>
> Regarding the error:
>
> [2015-05-02 02:00:09,800][INFO ][cluster.metadata ] [abc] 
> [logstash-2015.05.02] creating index, cause [auto(bulk api)], shards [5]/[1], 
> mappings [_default_]
> [2015-05-02 02:00:29,890][INFO ][cluster.metadata ] [abc] 
> [logstash-2015.05.02] update_mapping [syslog] (dynamic)
> [2015-05-02 02:00:31,581][INFO ][cluster.metadata ] [abc] 
> [logstash-2015.05.02] update_mapping [syslog] (dynamic)
> [2015-05-02 03:01:03,038][WARN ][index.engine.internal] [abc] 
> [logstash-2015.05.01][4] failed engine [out of memory]
> [2015-05-02 03:01:04,085][DEBUG][action.search.type   ] [abc] [2183065] 
> Failed to execute fetch phase
> org.elasticsearch.ElasticsearchException: Java heap space
> at 
> org.elasticsearch.ExceptionsHelper.convertToRuntime(ExceptionsHelper.java:40)
> at 
> org.elasticsearch.search.SearchService.executeFetchPhase(SearchService.java:467)
> at 
> org.elasticsearch.search.action.SearchServiceTransportAction$17.call(SearchServiceTransportAction.java:410)
> at 
> org.elasticsearch.search.action.SearchServiceTransportAction$17.call(SearchServiceTransportAction.java:407)
> at 
> org.elasticsearch.search.action.SearchServiceTransportAction$23.run(SearchServiceTransportAction.java:517)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.OutOfMemoryError: Java heap space
> at 
> org.apache.lucene.codecs.compressing.CompressionMode$4.decompress(CompressionMode.java:133)
> at 
> org.apache.lucene.codecs.compressing.CompressingStoredFieldsReader.visitDocument(CompressingStoredFieldsReader.java:347)
> at org.apache.lucene.index.SegmentReader.document(SegmentReader.java:288)
> at 
> org.apache.lucene.index.BaseCompositeReader.document(BaseCompositeReader.java:110)
> at org.apache.lucene.search.IndexSearcher.doc(IndexSearcher.java:196)
> at 
> org.elasticsearch.search.fetch.FetchPhase.loadStoredFields(FetchPhase.java:228)
> at org.elasticsearch.search.fetch.FetchPhase.execute(FetchPhase.java:156)
> at 
> org.elasticsearch.search.SearchService.executeFetchPhase(SearchService.java:455)
> ... 6 more
> [2015-05-02 03:01:35,204][WARN ][index.engine.internal] [abc] 
> [logstash-2015.05.02][2] failed engine [out of memory]
> [2015-05-02 03:01:07,133][WARN ][index.engine.internal] [abc] 
> [logstash-2015.05.01][4] failed to flush after setting shard to inactive
> org.elasticsearch.index.engine.FlushFailedEngineException: 
> [logstash-2015.05.01][4] Flush failed
> at 
> org.elasticsearch.index.engine.internal.InternalEngine.flush(InternalEngine.java:781)
> at 
> org.elasticsearch.index.engine.internal.InternalEngine.updateIndexingBufferSize(InternalEngine.java:233)
> at 
> org.elasticsearch.indices.memory.IndexingMemoryController$ShardsIndicesStatusChecker.run(IndexingMemoryController.java:201)
> at 
> org.elasticsearch.threadpool.ThreadPool$LoggingRunnable.run(ThreadPool.java:454)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.OutOfMemoryError: Java heap space
>
>
> Thanks in advance!
>
> BR
>
> Xiro
>
> --
> 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

Re: About replica shard use many field data

[Mark Walkom]

Replica's don't double the amount of field data loaded. A query will only
load what it needs from the shards it needs, but it won't load primary and
replica, just one or the other.

Ideally you should 1) upgrade to aggs, facets are deprecated and not as
performant, and 2) upgrade to doc_values.

On 4 May 2015 at 18:50, Junheng Gong  wrote:

> we have about 2.2B data in our elasticsearch, and we using facet and
> function score query on those data.
>
> it will load many data to fielddata, and replica double it.
>
> so my question is "how to set replica to make sure it won't use field data
> expect primary shard down"?
>
> --
> 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/83db33a6-0248-42eb-b913-8da49a45006f%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAEYi1X9ag56CtN%3D%3DnkMdNqfUfeOxgNEDTnKQ1LXtDZw%3DRuhzhw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Howto: extract (misspelled?) keywords from a string

[berco]

I'm still researching this but I have too little experience with it to draw 
a conclusion with certainty. Anyone of you ElesticSearch experts know 
whether ES is the right tool for the job?

On Saturday, May 2, 2015 at 5:54:11 PM UTC+2, be...@media2b.net wrote:
>
> I have a large collection of strings that each contain information about a 
> certain product. For example:
>
> wine Bardolo red 1L 12b 12% 
> La Tulipe, 13* box 3 bottles, 2005
> Great Johnny Walker 7CL 22% red label
> Wisky Jonny Walken .7 Red limited editon
>
> The number of product names is limited, as are most other properties, but 
> they might be misspelled. 
>
> I would like to extract keywords from all those strings. Product name, 
> product type, volume, etc. But I'm not sure what the best approach would be 
> and if ElasticSearch would be the tool of  choice. I've looked at 
> PostgreSQL's trigram plugin (pg_tgrm) since all data sits in a PostgreSQL 
> db at the moment, but that seems limited. I was thinking about creating 
> some kind of master list of proper keyword and try to match words from a 
> string with those keywords. These words could be misspelled meaning they 
> would have to be:
>
> 1. fuzzy matched
> 2. matched by hand
> 3. match by some sort of neural network trained with existing data
>
> Someone suggested "analyzing the entire string as an ngram using the ngram 
> tokenizer", but I'm not sure. Any pointers where I should direct my effort 
> would be highly appreciated!
>

-- 
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/3053bd4f-19ac-41e0-b1d9-bd6cb0409063%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

About replica shard use many field data

[Junheng Gong]

we have about 2.2B data in our elasticsearch, and we using facet and 
function score query on those data. 

it will load many data to fielddata, and replica double it.

so my question is "how to set replica to make sure it won't use field data 
expect primary shard down"?

-- 
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/83db33a6-0248-42eb-b913-8da49a45006f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Requirejs with Elasticsearch Angular app throwing Uncaught TypeError: _.extend is not a function

[Nithyanand]

I am trying to build Elasticsearch Angular app. I am using require.js.


main.js

-

require.config({
 
paths : {
'angular' : '../bower_components/angular/angular',
'elasticsearch' : '../bower_components/elasticsearch/elasticsearch',
'app' : 'app',
'coreModule':'coreModule',
'esClient' : 'service/esClient'
},

shim : {

'app':{
'deps' : ['angular','coreModule']
},

'coreModule' : {
'deps' :['angular', 'elasticsearch','esClient']   
},

'esClient' : {
'deps' :['angular', 'elasticsearch']   
}

}

});

require(['app'], function(){
   
   angular.bootstrap(document, ['app']); 
});



esClient.js



define(function(){
 
var esClient=angular.module('esClient', ['elasticsearch']);

esClient.service('client', function (esFactory) {
return esFactory({
host: 'http://localhost:9200',
apiVersion: '1.5',
log: 'trace'
});
});

});

--


But it is throwing the following errors. Anyone else faced this issue?

Uncaught TypeError: _.extend is not a function

40.__browserify_Buffer @ elasticsearch.angular.js:38901

s @ elasticsearch.angular.js:4

(anonymous function) @ elasticsearch.angular.js:4

24.../connection @ elasticsearch.angular.js:37262

s @ elasticsearch.angular.js:4

(anonymous function) @ elasticsearch.angular.js:4

15../lib/client @ elasticsearch.angular.js:18307

s @ elasticsearch.angular.js:4

e @ elasticsearch.angular.js:4

(anonymous function) @ elasticsearch.angular.js:4

Uncaught Error: [$injector:modulerr] Failed to instantiate module app due 
to:

Error: [$injector:modulerr] Failed to instantiate module coreModule due to:

Error: [$injector:modulerr] Failed to instantiate module esClient due to:

Error: [$injector:modulerr] Failed to instantiate module elasticsearch due 
to:

Error: [$injector:nomod] Module 'elasticsearch' is not available! You 
either misspelled the module name or forgot to load it. If registering a 
module ensure that you specify the dependencies as the second argument.

-- 
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/384687d4-1fc2-41d1-b510-061b6b112d13%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Elasticsearch crashing, Dashboards missing

[xiro86]

Hi,

I've set up ELK-Stack for Monitoring of our Firewall logging. It works 
fine, we have two dashboards rotating on a screen and are very happy with 
it. Unfortunately it crashed now already for the second time with the same 
error. This won't be that dramatic, since it works after a restart of the 
services - but the critical thing about it is, that the saved dashboards 
disappear also.

Since I can't figure out where the dashboards are saved, I can't even do a 
backup of them.

Is it even possible to backup the dashboard only - and where is it stored?

Regarding the error:

[2015-05-02 02:00:09,800][INFO ][cluster.metadata ] [abc] 
[logstash-2015.05.02] creating index, cause [auto(bulk api)], shards [5]/[1], 
mappings [_default_]
[2015-05-02 02:00:29,890][INFO ][cluster.metadata ] [abc] 
[logstash-2015.05.02] update_mapping [syslog] (dynamic)
[2015-05-02 02:00:31,581][INFO ][cluster.metadata ] [abc] 
[logstash-2015.05.02] update_mapping [syslog] (dynamic)
[2015-05-02 03:01:03,038][WARN ][index.engine.internal] [abc] 
[logstash-2015.05.01][4] failed engine [out of memory]
[2015-05-02 03:01:04,085][DEBUG][action.search.type   ] [abc] [2183065] 
Failed to execute fetch phase
org.elasticsearch.ElasticsearchException: Java heap space
at 
org.elasticsearch.ExceptionsHelper.convertToRuntime(ExceptionsHelper.java:40)
at 
org.elasticsearch.search.SearchService.executeFetchPhase(SearchService.java:467)
at 
org.elasticsearch.search.action.SearchServiceTransportAction$17.call(SearchServiceTransportAction.java:410)
at 
org.elasticsearch.search.action.SearchServiceTransportAction$17.call(SearchServiceTransportAction.java:407)
at 
org.elasticsearch.search.action.SearchServiceTransportAction$23.run(SearchServiceTransportAction.java:517)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.OutOfMemoryError: Java heap space
at 
org.apache.lucene.codecs.compressing.CompressionMode$4.decompress(CompressionMode.java:133)
at 
org.apache.lucene.codecs.compressing.CompressingStoredFieldsReader.visitDocument(CompressingStoredFieldsReader.java:347)
at org.apache.lucene.index.SegmentReader.document(SegmentReader.java:288)
at 
org.apache.lucene.index.BaseCompositeReader.document(BaseCompositeReader.java:110)
at org.apache.lucene.search.IndexSearcher.doc(IndexSearcher.java:196)
at 
org.elasticsearch.search.fetch.FetchPhase.loadStoredFields(FetchPhase.java:228)
at org.elasticsearch.search.fetch.FetchPhase.execute(FetchPhase.java:156)
at 
org.elasticsearch.search.SearchService.executeFetchPhase(SearchService.java:455)
... 6 more
[2015-05-02 03:01:35,204][WARN ][index.engine.internal] [abc] 
[logstash-2015.05.02][2] failed engine [out of memory]
[2015-05-02 03:01:07,133][WARN ][index.engine.internal] [abc] 
[logstash-2015.05.01][4] failed to flush after setting shard to inactive
org.elasticsearch.index.engine.FlushFailedEngineException: 
[logstash-2015.05.01][4] Flush failed
at 
org.elasticsearch.index.engine.internal.InternalEngine.flush(InternalEngine.java:781)
at 
org.elasticsearch.index.engine.internal.InternalEngine.updateIndexingBufferSize(InternalEngine.java:233)
at 
org.elasticsearch.indices.memory.IndexingMemoryController$ShardsIndicesStatusChecker.run(IndexingMemoryController.java:201)
at 
org.elasticsearch.threadpool.ThreadPool$LoggingRunnable.run(ThreadPool.java:454)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.OutOfMemoryError: Java heap space


Thanks in advance!

BR

Xiro

-- 
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/c8af2bf3-35f3-4fa5-88f3-2e8bc922932b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: ES upgrade

[Mark Walkom]

You need to open 9300 between nodes to allow them to communicate, that's
likely the cause of this.

On 4 May 2015 at 16:06,  wrote:

> yes mark I am running same es version and java on both nodes.i have
> iptables settings in my nodes is this be a problem? do we need to allow any
> ports to resolve this issue I already allowed nodes communication ports
> before..
>
>  Java version "1.7.0_75"
> Java(TM) SE Runtime Environment (build 1.7.0_75-b13)
> Java HotSpot(TM) 64-Bit Server VM (build 24.75-b04, mixed mode)
>
> java version "1.7.0_75"
> Java(TM) SE Runtime Environment (build 1.7.0_75-b13)
> Java HotSpot(TM) 64-Bit Server VM (build 24.75-b04, mixed mode)
>
>
> On Saturday, May 2, 2015 at 2:36:31 AM UTC+5:30, Mark Walkom wrote:
>>
>> Are you running the same ES and java versions on all your nodes and
>> clients?
>>
>> On 1 May 2015 at 21:21,  wrote:
>>
>>> Hi All
>>>
>>>i upgraded elastic search from 1.4.2 to  1.5.2 i am getting following
>>> warning from console after upgrade please explain me the following error
>>> why it is coming.
>>>
>>> [2015-05-01 06:15:13,361][WARN ][transport.netty  ] [ES_Node1]
>>> exception caught on transport layer [[id: 0xc483723b, /:3845 =>
>>> /:9300]], closing connection
>>> java.io.StreamCorruptedException: invalid internal transport message
>>> format, got (47,45,54,20)
>>> at
>>> org.elasticsearch.transport.netty.SizeHeaderFrameDecoder.decode(SizeHeaderFrameDecoder.java:47)
>>> at
>>> org.elasticsearch.common.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:425)
>>> at
>>> org.elasticsearch.common.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:303)
>>> at
>>> org.elasticsearch.common.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70)
>>> at
>>> org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)
>>> at
>>> org.elasticsearch.common.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791)
>>> at
>>> org.elasticsearch.common.netty.OpenChannelsHandler.handleUpstream(OpenChannelsHandler.java:74)
>>> at
>>> org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)
>>> at
>>> org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:559)
>>> at
>>> org.elasticsearch.common.netty.channel.Channels.fireMessageReceived(Channels.java:268)
>>> at
>>> org.elasticsearch.common.netty.channel.Channels.fireMessageReceived(Channels.java:255)
>>> at
>>> org.elasticsearch.common.netty.channel.socket.nio.NioWorker.read(NioWorker.java:88)
>>> at
>>> org.elasticsearch.common.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:108)
>>> at
>>> org.elasticsearch.common.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:337)
>>> at
>>> org.elasticsearch.common.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:89)
>>> at
>>> org.elasticsearch.common.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178)
>>> at
>>> org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
>>> at
>>> org.elasticsearch.common.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
>>> at
>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>>> at
>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>>>
>>>
>>> Thanks
>>> phani
>>>
>>>  --
>>> 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/341f2003-4211-4c70-aebf-a8d1fa649820%40googlegroups.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>  --
> 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/19ab1ec0-8392-48c6-8c68-14bcefae7ec4%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscrib

Re: Scaling problem

[Jason Wee]

read these links, it should answer your question.

http://www.elastic.co/guide/en/elasticsearch/client/java-api/1.x/client.html#transport-client
http://www.elastic.co/guide/en/elasticsearch/guide/current/_transport_client_versus_node_client.html

jason



On Mon, May 4, 2015 at 2:45 PM, Shohedul Hasan 
wrote:

> Yes i am using transport client, i can add the all servers' address in
> transport client instantiation. But how do ES server will know each other
> ?? And are you telling me that i don't need to use Nginx as load balancer,
> ES transport client will automatically do it for me ??
>
> On Monday, May 4, 2015 at 12:35:10 PM UTC+6, Jason Wee wrote:
>>
>> If you are using java transport client in elasticsearch, you just add one
>> of the elasticsearch node with setting sniff to on. The the transport
>> client should have all the information it needed. When the transport client
>> index, iirc, it is in round robin fashion. The es cluster node is
>> intelligent enough to replicate the write to the other es nodes.
>>
>> hth
>>
>> jason
>>
>> On Mon, May 4, 2015 at 2:12 PM, Shohedul Hasan 
>> wrote:
>>
>>> Hi,
>>> I have installed ES in one server. I want to create 3-4 servers for my
>>> ES cluster.  But when i send request in which server i should send from my
>>> java code and how? I have read once, putting one user's data in one primary
>>> shard helps to improve performance. I have also read that using Nginx as
>>> load balancer also improve performance. Now my question is, how can i put
>>> these two things together?  Also how one ES server knows about other ES
>>> servers ? Finally can you give me some useful links by which i can try to
>>> scale ES in multiple server.
>>>
>>> --
>>> 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/345f86bd-bf6d-4f10-9ef3-7f429b0b17f5%40googlegroups.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>  --
> 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/c6b6562c-c01d-449c-a9e3-705d4ffadfd0%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAHO4itxwid6DSoS%3DyafCZXrxx-z0_AKLPdZEwjNQn-nNBMd4xA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.