Re: Cluster issue in production, split brain?
we are on 1.3.2 version. I have looked in other threads for similar issues, but they seem to be on very old versions. please let me know how to avoid such split brain issues. thank you. On Wednesday, February 18, 2015 at 7:18:29 PM UTC-6, Nara Alzapur wrote: thank you for the reply. Yes. They are in same DC. I thought n + 1 /2 scenario would apply and such issue would not occur. Wonder how can a node be part of 2 clusters at the same time? any config changes i can do to avoid such issue? On Wednesday, February 18, 2015 at 7:13:39 PM UTC-6, Mark Walkom wrote: This is a split brain scenario. Are your nodes in the same DC? On 19 February 2015 at 11:40, Nara Alzapur avn...@gmail.com wrote: I saw an issue with cluster in production today. we have a cluster of 3 ( master data ) nodes and min number of master nodes is set to 2 in config. at some point due to network issue, server 3 couldnt connect to 2, but could connect to 1..so it had an active cluster with 1 3 and 3 is primary. On 2 bigdesk showed, cluster with 1 2 and 2 being primary. is this a split brain scenario? i assume not because same cluster name and 1 is part of both. bigdesk on 2 3 showed green. however we saw disc IO shot up to 100%, and inconsistency on displaying data depending on which node the data was read from. After i restarted service on node 3, it was all fine, all 3 nodes were in cluster on bigdesk on all machines. can anyone please help me how cluster can get into such state, and how to avoid such scenario? thank you. -- 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/cb3f75e8-49f5-48fc-be93-9bb444ee56df%40googlegroups.com https://groups.google.com/d/msgid/elasticsearch/cb3f75e8-49f5-48fc-be93-9bb444ee56df%40googlegroups.com?utm_medium=emailutm_source=footer . 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/e9d75ac2-451f-496c-adef-b630d1f9dc8d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Help with 4 node cluster
you can make all nodes as master + data by setting following in elasticsearch.yml file. i dont think/know if you can setup 2 nodes as primary in cluster. For each index, you can set number of replica as 1 or more, so ES will automatically move them to different nodes than primary shard. i recommend using unicast for discovery as shown below if you have static IPs. node.master: true node.data: true discovery.zen.ping.multicast.enabled: false discovery.zen.ping.unicast.hosts: [IP1, IP2] On Wednesday, February 18, 2015 at 5:39:54 AM UTC-6, sysads wrote: Hi I am in need of help on setting up a 4 node elasticsearch servers. I have installed and configured ES on all 4 nodes but I am lost as to what the configuration in elasticsearch.yml will be: - if I want to have all 4 nodes both master and data - make node A act as primary shard while node B acts as its replica then node C as primary shard while node D as its own replica. 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/e73c6d3e-e0dd-4403-87d9-3ab922bb974f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Cluster issue in production, split brain?
thank you for the reply. Yes. They are in same DC. I thought n + 1 /2 scenario would apply and such issue would not occur. Wonder how can a node be part of 2 clusters at the same time? any config changes i can do to avoid such issue? On Wednesday, February 18, 2015 at 7:13:39 PM UTC-6, Mark Walkom wrote: This is a split brain scenario. Are your nodes in the same DC? On 19 February 2015 at 11:40, Nara Alzapur avn...@gmail.com javascript: wrote: I saw an issue with cluster in production today. we have a cluster of 3 ( master data ) nodes and min number of master nodes is set to 2 in config. at some point due to network issue, server 3 couldnt connect to 2, but could connect to 1..so it had an active cluster with 1 3 and 3 is primary. On 2 bigdesk showed, cluster with 1 2 and 2 being primary. is this a split brain scenario? i assume not because same cluster name and 1 is part of both. bigdesk on 2 3 showed green. however we saw disc IO shot up to 100%, and inconsistency on displaying data depending on which node the data was read from. After i restarted service on node 3, it was all fine, all 3 nodes were in cluster on bigdesk on all machines. can anyone please help me how cluster can get into such state, and how to avoid such scenario? thank you. -- You received this message because you are subscribed to the Google Groups elasticsearch group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearc...@googlegroups.com javascript:. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/cb3f75e8-49f5-48fc-be93-9bb444ee56df%40googlegroups.com https://groups.google.com/d/msgid/elasticsearch/cb3f75e8-49f5-48fc-be93-9bb444ee56df%40googlegroups.com?utm_medium=emailutm_source=footer . 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/5e81fa7d-ac82-4fce-9d0f-971abb7ab71a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Cluster issue in production, split brain?
I saw an issue with cluster in production today. we have a cluster of 3 ( master data ) nodes and min number of master nodes is set to 2 in config. at some point due to network issue, server 3 couldnt connect to 2, but could connect to 1..so it had an active cluster with 1 3 and 3 is primary. On 2 bigdesk showed, cluster with 1 2 and 2 being primary. is this a split brain scenario? i assume not because same cluster name and 1 is part of both. bigdesk on 2 3 showed green. however we saw disc IO shot up to 100%, and inconsistency on displaying data depending on which node the data was read from. After i restarted service on node 3, it was all fine, all 3 nodes were in cluster on bigdesk on all machines. can anyone please help me how cluster can get into such state, and how to avoid such scenario? thank you. -- 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/cb3f75e8-49f5-48fc-be93-9bb444ee56df%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
GC issue
i have setup elasticsearch on a windows box and set ES_HEAP_SIZE to 10g out of total 28g. For some reason, GC keeps happening as soon as heap memory reaches around 250mb. Attached couple of images from BigDesk. Please let me know how to avoid this. ES version: 1.3.2 Java Version: VM name: Java HotSpot(TM) 64-Bit Server VM VM vendor: Oracle Corporation VM version: 25.20-b23 Uptime: 14.9h Java version: 1.8.0_20 -- 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/dfe576de-2f80-49d3-8f8b-f9464b0f24ff%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
default mapping for string - analyzed vs non_analyzed
hi,
we are using elasticsearch to generate default mapping whenever we index
the document. we cannot really control the document fields, as we let our
clients define custom fields and we index them automatically, so we have to
rely on elasticsearch generating the mapping for us.
one issue i am facing right now is for strings, we allow users to sort. if
strings are not analyzed, the sort results are not accurate. is there any
way to configure elasticsearch to generate default mapping of a field with
both as analyzed, and not_analyzed. for example, say i index this document
post /myindex/app/1
{
name: full name
}
i would like it generate the mapping as
{
app:{
properties:{
name: {
type: string,
fields: {
raw: { type: string, index: not_analyzed }
}
}
}
}
}
raw is something that can configure, so i can use it in my application.
thank you.
--
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/40b5e927-13ab-46dc-9f1d-bd34e71279d3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
default mapping for strings : analyzed vs non_analyzed
hi,
we are using elasticsearch to generate default mapping whenever we index
the document. we cannot really control the document fields, as we let our
clients define custom fields and we index them automatically, so we have to
rely on elasticsearch generating the mapping for us.
one issue i am facing right now is for strings, we allow users to sort. if
strings are not analyzed, the sort results are not accurate. is there any
way to configure elasticsearch to generate default mapping of a field with
both as analyzed, and not_analyzed. for example, say i index this document
post /myindex/app/1
{
name: full name
}
i would like it generate the mapping as
{
app:{
properties:{
name: {
type: string,
fields: {
raw: { type: string, index: not_analyzed }
}
}
}
}
}
raw is something that can configure, so i can use it in my application.
thank you.
--
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/6fdc14b3-c48b-437b-bcb4-347bccb7d1d9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
