not enough master nodes discovered during pinging - Elasticsearch cluster self signed certificateHow to create a self-signed certificate with OpenSSLcURL PHP Proper SSL between private servers with self-signed certificateHow could I set up a ES cluster?Elasticsearch cluster initializationData node can’t find master node ,but master can find data node in ElasticsearchHow to configure two nodes to connect to same cluster in elasticsearch?Can't start Elasticsearch (fileInputStream Fail)Could not able to connect to with Elastic search clusterAdding coordinating or client node to my existing elasticsearch cluster

How to get a large amount of cash abroad if a debit card stops working?

Why is the air inside airliners so dry (low humidity)?

On how/if I should ask my supervisor about lead authorship?

What happens if a country signs mutual defense treaties with several countries who later go to war with each other?

Dodging a Deathbeam travelling at speed of light

Call local emergency number using a foreign mobile number

MOS 8502, just a 6510B?

Hikers in Halloween

Double features: The wrap-up

Setting PS1 color

Does the original Game Boy game "Tetris" have a battery memory inside the cartridge?

In what way were Renaissance battles like chess matches?

Wood versus marble rolling pin 'performance'

Is it possible to save a (science) PhD in 10 months?

Double feature: Bibliophile edition

Is an SSH key with a passphrase a 2FA?

Have supporters of "right-wing populist" parties in Europe explained why they trust Trump?

Gold plating versus Silver plating for electrical contacts?

How to Keep Winged People Where They Belong?

English equivalent of the Malayalam saying "don't stab/poke the dead body"?

What does it take to make metal music?

Why would gloves be necessary for handling flobberworms?

ASCII Pumpkin Carving

Cheat at Rock-Paper-Scissors-Lizard-Spock



not enough master nodes discovered during pinging - Elasticsearch cluster self signed certificate


How to create a self-signed certificate with OpenSSLcURL PHP Proper SSL between private servers with self-signed certificateHow could I set up a ES cluster?Elasticsearch cluster initializationData node can’t find master node ,but master can find data node in ElasticsearchHow to configure two nodes to connect to same cluster in elasticsearch?Can't start Elasticsearch (fileInputStream Fail)Could not able to connect to with Elastic search clusterAdding coordinating or client node to my existing elasticsearch cluster






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty
margin-bottom:0;









0

















I used SearchGuard to encrypt nodes in ElasticSearch cluster following this guide



Master:



cluster.name: client1
searchguard.enterprise_modules_enabled: false


node.name: ekl.test.com
node.master: true
node.data: true
node.ingest: true


network.host: 0.0.0.0

#http.host: 0.0.0.0
network.publish_host: ["ekl1.test1.com","ekl.test.com"]



http.port: 9200


discovery.zen.ping.unicast.hosts: ["ekl.test.com", "ekl1.test1.com"]


discovery.zen.minimum_master_nodes: 1

xpack.security.enabled: false


searchguard.ssl.transport.pemcert_filepath: '/etc/elasticsearch/ssl/node1.pem'
searchguard.ssl.transport.pemkey_filepath: 'ssl/node1.key'
searchguard.ssl.transport.pemtrustedcas_filepath: '/etc/elasticsearch/ssl/root-ca.pem'
searchguard.ssl.transport.enforce_hostname_verification: false
searchguard.ssl.transport.resolve_hostname: false
searchguard.ssl.http.enabled: true
searchguard.ssl.http.pemcert_filepath: '/etc/elasticsearch/ssl/node1_http.pem'
searchguard.ssl.http.pemkey_filepath: '/etc/elasticsearch/ssl/node1_http.key'
searchguard.ssl.http.pemtrustedcas_filepath: '/etc/elasticsearch/ssl/root-ca.pem'
searchguard.nodes_dn:
- CN=ekl.test.com,OU=Ops,O=BugBear BG, Ltd.,DC=BugBear,DC=com
- CN=ekl1.test1.com,OU=Ops,O=BugBear BG, Ltd.,DC=BugBear,DC=com
searchguard.authcz.admin_dn:
- CN=admin.test.com,OU=Ops,O=BugBear Com, Inc.,DC=example,DC=com


Node:



cluster.name: client1
searchguard.enterprise_modules_enabled: false


node.name: ekl1.test.com
node.master: false
node.data: true
node.ingest: false


network.host: 0.0.0.0

#http.host: 0.0.0.0
network.publish_host: ["ekl1.test1.com","ekl.test.com"]



http.port: 9200


discovery.zen.ping.unicast.hosts: ["ekl.test.com", "ekl1.test1.com"]


discovery.zen.minimum_master_nodes: 1

xpack.security.enabled: false


searchguard.ssl.transport.pemcert_filepath: '/etc/elasticsearch/ssl/node2.pem'
searchguard.ssl.transport.pemkey_filepath: 'ssl/node2.key'
searchguard.ssl.transport.pemtrustedcas_filepath: '/etc/elasticsearch/ssl/root-ca.pem'
searchguard.ssl.transport.enforce_hostname_verification: false
searchguard.ssl.transport.resolve_hostname: false
searchguard.ssl.http.enabled: true
searchguard.ssl.http.pemcert_filepath: '/etc/elasticsearch/ssl/node2_http.pem'
searchguard.ssl.http.pemkey_filepath: '/etc/elasticsearch/ssl/node2_http.key'
searchguard.ssl.http.pemtrustedcas_filepath: '/etc/elasticsearch/ssl/root-ca.pem'
searchguard.nodes_dn:
- CN=ekl.test.com,OU=Ops,O=BugBear BG, Ltd.,DC=BugBear,DC=com
- CN=ekl1.test1.com,OU=Ops,O=BugBear BG, Ltd.,DC=BugBear,DC=com
searchguard.authcz.admin_dn:
- CN=admin.test.com,OU=Ops,O=BugBear Com, Inc.,DC=example,DC=com
Certificates are self-signed


From node i can telnet to ports 9200/9300 by hostnames i can ping and



curl -kvX GET "https://admin:pass@ekl.test.com:9200" works fine.
Errors on node:



[ekl1.test1.com] not enough master nodes discovered during pinging (found [], but needed 1), pinging again



Both server names are correct



I suspect issue is in self-signed certificate i imported it in trusted root CA anchor but error remained.



If i specify IP instead of hostnames then getting:



Illegal parameter in http or transport request found.
This means that one node is trying to connect to another with
a non-node certificate (no OID or searchguard.nodes_dn incorrect configured) or that someone
is spoofing requests.




ES Config path is /etc/elasticsearch
[2019-03-28T21:25:56,450][INFO ][c.f.s.s.DefaultSearchGuardKeyStore] >[ekl1.test1.com] OpenSSL not available (this is not an error, we simply >fallback to built-in JDK SSL) because of java.lang.ClassNotFoundException: >io.netty.internal.tcnative.SSL











share|improve this question


































    0

















    I used SearchGuard to encrypt nodes in ElasticSearch cluster following this guide



    Master:



    cluster.name: client1
    searchguard.enterprise_modules_enabled: false


    node.name: ekl.test.com
    node.master: true
    node.data: true
    node.ingest: true


    network.host: 0.0.0.0

    #http.host: 0.0.0.0
    network.publish_host: ["ekl1.test1.com","ekl.test.com"]



    http.port: 9200


    discovery.zen.ping.unicast.hosts: ["ekl.test.com", "ekl1.test1.com"]


    discovery.zen.minimum_master_nodes: 1

    xpack.security.enabled: false


    searchguard.ssl.transport.pemcert_filepath: '/etc/elasticsearch/ssl/node1.pem'
    searchguard.ssl.transport.pemkey_filepath: 'ssl/node1.key'
    searchguard.ssl.transport.pemtrustedcas_filepath: '/etc/elasticsearch/ssl/root-ca.pem'
    searchguard.ssl.transport.enforce_hostname_verification: false
    searchguard.ssl.transport.resolve_hostname: false
    searchguard.ssl.http.enabled: true
    searchguard.ssl.http.pemcert_filepath: '/etc/elasticsearch/ssl/node1_http.pem'
    searchguard.ssl.http.pemkey_filepath: '/etc/elasticsearch/ssl/node1_http.key'
    searchguard.ssl.http.pemtrustedcas_filepath: '/etc/elasticsearch/ssl/root-ca.pem'
    searchguard.nodes_dn:
    - CN=ekl.test.com,OU=Ops,O=BugBear BG, Ltd.,DC=BugBear,DC=com
    - CN=ekl1.test1.com,OU=Ops,O=BugBear BG, Ltd.,DC=BugBear,DC=com
    searchguard.authcz.admin_dn:
    - CN=admin.test.com,OU=Ops,O=BugBear Com, Inc.,DC=example,DC=com


    Node:



    cluster.name: client1
    searchguard.enterprise_modules_enabled: false


    node.name: ekl1.test.com
    node.master: false
    node.data: true
    node.ingest: false


    network.host: 0.0.0.0

    #http.host: 0.0.0.0
    network.publish_host: ["ekl1.test1.com","ekl.test.com"]



    http.port: 9200


    discovery.zen.ping.unicast.hosts: ["ekl.test.com", "ekl1.test1.com"]


    discovery.zen.minimum_master_nodes: 1

    xpack.security.enabled: false


    searchguard.ssl.transport.pemcert_filepath: '/etc/elasticsearch/ssl/node2.pem'
    searchguard.ssl.transport.pemkey_filepath: 'ssl/node2.key'
    searchguard.ssl.transport.pemtrustedcas_filepath: '/etc/elasticsearch/ssl/root-ca.pem'
    searchguard.ssl.transport.enforce_hostname_verification: false
    searchguard.ssl.transport.resolve_hostname: false
    searchguard.ssl.http.enabled: true
    searchguard.ssl.http.pemcert_filepath: '/etc/elasticsearch/ssl/node2_http.pem'
    searchguard.ssl.http.pemkey_filepath: '/etc/elasticsearch/ssl/node2_http.key'
    searchguard.ssl.http.pemtrustedcas_filepath: '/etc/elasticsearch/ssl/root-ca.pem'
    searchguard.nodes_dn:
    - CN=ekl.test.com,OU=Ops,O=BugBear BG, Ltd.,DC=BugBear,DC=com
    - CN=ekl1.test1.com,OU=Ops,O=BugBear BG, Ltd.,DC=BugBear,DC=com
    searchguard.authcz.admin_dn:
    - CN=admin.test.com,OU=Ops,O=BugBear Com, Inc.,DC=example,DC=com
    Certificates are self-signed


    From node i can telnet to ports 9200/9300 by hostnames i can ping and



    curl -kvX GET "https://admin:pass@ekl.test.com:9200" works fine.
    Errors on node:



    [ekl1.test1.com] not enough master nodes discovered during pinging (found [], but needed 1), pinging again



    Both server names are correct



    I suspect issue is in self-signed certificate i imported it in trusted root CA anchor but error remained.



    If i specify IP instead of hostnames then getting:



    Illegal parameter in http or transport request found.
    This means that one node is trying to connect to another with
    a non-node certificate (no OID or searchguard.nodes_dn incorrect configured) or that someone
    is spoofing requests.




    ES Config path is /etc/elasticsearch
    [2019-03-28T21:25:56,450][INFO ][c.f.s.s.DefaultSearchGuardKeyStore] >[ekl1.test1.com] OpenSSL not available (this is not an error, we simply >fallback to built-in JDK SSL) because of java.lang.ClassNotFoundException: >io.netty.internal.tcnative.SSL











    share|improve this question






























      0












      0








      0








      I used SearchGuard to encrypt nodes in ElasticSearch cluster following this guide



      Master:



      cluster.name: client1
      searchguard.enterprise_modules_enabled: false


      node.name: ekl.test.com
      node.master: true
      node.data: true
      node.ingest: true


      network.host: 0.0.0.0

      #http.host: 0.0.0.0
      network.publish_host: ["ekl1.test1.com","ekl.test.com"]



      http.port: 9200


      discovery.zen.ping.unicast.hosts: ["ekl.test.com", "ekl1.test1.com"]


      discovery.zen.minimum_master_nodes: 1

      xpack.security.enabled: false


      searchguard.ssl.transport.pemcert_filepath: '/etc/elasticsearch/ssl/node1.pem'
      searchguard.ssl.transport.pemkey_filepath: 'ssl/node1.key'
      searchguard.ssl.transport.pemtrustedcas_filepath: '/etc/elasticsearch/ssl/root-ca.pem'
      searchguard.ssl.transport.enforce_hostname_verification: false
      searchguard.ssl.transport.resolve_hostname: false
      searchguard.ssl.http.enabled: true
      searchguard.ssl.http.pemcert_filepath: '/etc/elasticsearch/ssl/node1_http.pem'
      searchguard.ssl.http.pemkey_filepath: '/etc/elasticsearch/ssl/node1_http.key'
      searchguard.ssl.http.pemtrustedcas_filepath: '/etc/elasticsearch/ssl/root-ca.pem'
      searchguard.nodes_dn:
      - CN=ekl.test.com,OU=Ops,O=BugBear BG, Ltd.,DC=BugBear,DC=com
      - CN=ekl1.test1.com,OU=Ops,O=BugBear BG, Ltd.,DC=BugBear,DC=com
      searchguard.authcz.admin_dn:
      - CN=admin.test.com,OU=Ops,O=BugBear Com, Inc.,DC=example,DC=com


      Node:



      cluster.name: client1
      searchguard.enterprise_modules_enabled: false


      node.name: ekl1.test.com
      node.master: false
      node.data: true
      node.ingest: false


      network.host: 0.0.0.0

      #http.host: 0.0.0.0
      network.publish_host: ["ekl1.test1.com","ekl.test.com"]



      http.port: 9200


      discovery.zen.ping.unicast.hosts: ["ekl.test.com", "ekl1.test1.com"]


      discovery.zen.minimum_master_nodes: 1

      xpack.security.enabled: false


      searchguard.ssl.transport.pemcert_filepath: '/etc/elasticsearch/ssl/node2.pem'
      searchguard.ssl.transport.pemkey_filepath: 'ssl/node2.key'
      searchguard.ssl.transport.pemtrustedcas_filepath: '/etc/elasticsearch/ssl/root-ca.pem'
      searchguard.ssl.transport.enforce_hostname_verification: false
      searchguard.ssl.transport.resolve_hostname: false
      searchguard.ssl.http.enabled: true
      searchguard.ssl.http.pemcert_filepath: '/etc/elasticsearch/ssl/node2_http.pem'
      searchguard.ssl.http.pemkey_filepath: '/etc/elasticsearch/ssl/node2_http.key'
      searchguard.ssl.http.pemtrustedcas_filepath: '/etc/elasticsearch/ssl/root-ca.pem'
      searchguard.nodes_dn:
      - CN=ekl.test.com,OU=Ops,O=BugBear BG, Ltd.,DC=BugBear,DC=com
      - CN=ekl1.test1.com,OU=Ops,O=BugBear BG, Ltd.,DC=BugBear,DC=com
      searchguard.authcz.admin_dn:
      - CN=admin.test.com,OU=Ops,O=BugBear Com, Inc.,DC=example,DC=com
      Certificates are self-signed


      From node i can telnet to ports 9200/9300 by hostnames i can ping and



      curl -kvX GET "https://admin:pass@ekl.test.com:9200" works fine.
      Errors on node:



      [ekl1.test1.com] not enough master nodes discovered during pinging (found [], but needed 1), pinging again



      Both server names are correct



      I suspect issue is in self-signed certificate i imported it in trusted root CA anchor but error remained.



      If i specify IP instead of hostnames then getting:



      Illegal parameter in http or transport request found.
      This means that one node is trying to connect to another with
      a non-node certificate (no OID or searchguard.nodes_dn incorrect configured) or that someone
      is spoofing requests.




      ES Config path is /etc/elasticsearch
      [2019-03-28T21:25:56,450][INFO ][c.f.s.s.DefaultSearchGuardKeyStore] >[ekl1.test1.com] OpenSSL not available (this is not an error, we simply >fallback to built-in JDK SSL) because of java.lang.ClassNotFoundException: >io.netty.internal.tcnative.SSL











      share|improve this question

















      I used SearchGuard to encrypt nodes in ElasticSearch cluster following this guide



      Master:



      cluster.name: client1
      searchguard.enterprise_modules_enabled: false


      node.name: ekl.test.com
      node.master: true
      node.data: true
      node.ingest: true


      network.host: 0.0.0.0

      #http.host: 0.0.0.0
      network.publish_host: ["ekl1.test1.com","ekl.test.com"]



      http.port: 9200


      discovery.zen.ping.unicast.hosts: ["ekl.test.com", "ekl1.test1.com"]


      discovery.zen.minimum_master_nodes: 1

      xpack.security.enabled: false


      searchguard.ssl.transport.pemcert_filepath: '/etc/elasticsearch/ssl/node1.pem'
      searchguard.ssl.transport.pemkey_filepath: 'ssl/node1.key'
      searchguard.ssl.transport.pemtrustedcas_filepath: '/etc/elasticsearch/ssl/root-ca.pem'
      searchguard.ssl.transport.enforce_hostname_verification: false
      searchguard.ssl.transport.resolve_hostname: false
      searchguard.ssl.http.enabled: true
      searchguard.ssl.http.pemcert_filepath: '/etc/elasticsearch/ssl/node1_http.pem'
      searchguard.ssl.http.pemkey_filepath: '/etc/elasticsearch/ssl/node1_http.key'
      searchguard.ssl.http.pemtrustedcas_filepath: '/etc/elasticsearch/ssl/root-ca.pem'
      searchguard.nodes_dn:
      - CN=ekl.test.com,OU=Ops,O=BugBear BG, Ltd.,DC=BugBear,DC=com
      - CN=ekl1.test1.com,OU=Ops,O=BugBear BG, Ltd.,DC=BugBear,DC=com
      searchguard.authcz.admin_dn:
      - CN=admin.test.com,OU=Ops,O=BugBear Com, Inc.,DC=example,DC=com


      Node:



      cluster.name: client1
      searchguard.enterprise_modules_enabled: false


      node.name: ekl1.test.com
      node.master: false
      node.data: true
      node.ingest: false


      network.host: 0.0.0.0

      #http.host: 0.0.0.0
      network.publish_host: ["ekl1.test1.com","ekl.test.com"]



      http.port: 9200


      discovery.zen.ping.unicast.hosts: ["ekl.test.com", "ekl1.test1.com"]


      discovery.zen.minimum_master_nodes: 1

      xpack.security.enabled: false


      searchguard.ssl.transport.pemcert_filepath: '/etc/elasticsearch/ssl/node2.pem'
      searchguard.ssl.transport.pemkey_filepath: 'ssl/node2.key'
      searchguard.ssl.transport.pemtrustedcas_filepath: '/etc/elasticsearch/ssl/root-ca.pem'
      searchguard.ssl.transport.enforce_hostname_verification: false
      searchguard.ssl.transport.resolve_hostname: false
      searchguard.ssl.http.enabled: true
      searchguard.ssl.http.pemcert_filepath: '/etc/elasticsearch/ssl/node2_http.pem'
      searchguard.ssl.http.pemkey_filepath: '/etc/elasticsearch/ssl/node2_http.key'
      searchguard.ssl.http.pemtrustedcas_filepath: '/etc/elasticsearch/ssl/root-ca.pem'
      searchguard.nodes_dn:
      - CN=ekl.test.com,OU=Ops,O=BugBear BG, Ltd.,DC=BugBear,DC=com
      - CN=ekl1.test1.com,OU=Ops,O=BugBear BG, Ltd.,DC=BugBear,DC=com
      searchguard.authcz.admin_dn:
      - CN=admin.test.com,OU=Ops,O=BugBear Com, Inc.,DC=example,DC=com
      Certificates are self-signed


      From node i can telnet to ports 9200/9300 by hostnames i can ping and



      curl -kvX GET "https://admin:pass@ekl.test.com:9200" works fine.
      Errors on node:



      [ekl1.test1.com] not enough master nodes discovered during pinging (found [], but needed 1), pinging again



      Both server names are correct



      I suspect issue is in self-signed certificate i imported it in trusted root CA anchor but error remained.



      If i specify IP instead of hostnames then getting:



      Illegal parameter in http or transport request found.
      This means that one node is trying to connect to another with
      a non-node certificate (no OID or searchguard.nodes_dn incorrect configured) or that someone
      is spoofing requests.




      ES Config path is /etc/elasticsearch
      [2019-03-28T21:25:56,450][INFO ][c.f.s.s.DefaultSearchGuardKeyStore] >[ekl1.test1.com] OpenSSL not available (this is not an error, we simply >fallback to built-in JDK SSL) because of java.lang.ClassNotFoundException: >io.netty.internal.tcnative.SSL








      elasticsearch ssl-certificate






      share|improve this question
















      share|improve this question













      share|improve this question




      share|improve this question








      edited Mar 28 at 22:37







      Milister

















      asked Mar 28 at 21:20









      MilisterMilister

      3171 silver badge18 bronze badges




      3171 silver badge18 bronze badges

























          1 Answer
          1






          active

          oldest

          votes


















          0


















          Found it: had to add to non-master:



          transport.tcp.port: 9300
          discovery.zen.ping.unicast.hosts: ["ekl.test.com:9300"]
          transport.host: ekl1.test1.com





          share|improve this answer



























            Your Answer






            StackExchange.ifUsing("editor", function ()
            StackExchange.using("externalEditor", function ()
            StackExchange.using("snippets", function ()
            StackExchange.snippets.init();
            );
            );
            , "code-snippets");

            StackExchange.ready(function()
            var channelOptions =
            tags: "".split(" "),
            id: "1"
            ;
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function()
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled)
            StackExchange.using("snippets", function()
            createEditor();
            );

            else
            createEditor();

            );

            function createEditor()
            StackExchange.prepareEditor(
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader:
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/4.0/"u003ecc by-sa 4.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            ,
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            );



            );














            draft saved

            draft discarded
















            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55407015%2fnot-enough-master-nodes-discovered-during-pinging-elasticsearch-cluster-self-s%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown


























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0


















            Found it: had to add to non-master:



            transport.tcp.port: 9300
            discovery.zen.ping.unicast.hosts: ["ekl.test.com:9300"]
            transport.host: ekl1.test1.com





            share|improve this answer






























              0


















              Found it: had to add to non-master:



              transport.tcp.port: 9300
              discovery.zen.ping.unicast.hosts: ["ekl.test.com:9300"]
              transport.host: ekl1.test1.com





              share|improve this answer




























                0














                0










                0









                Found it: had to add to non-master:



                transport.tcp.port: 9300
                discovery.zen.ping.unicast.hosts: ["ekl.test.com:9300"]
                transport.host: ekl1.test1.com





                share|improve this answer














                Found it: had to add to non-master:



                transport.tcp.port: 9300
                discovery.zen.ping.unicast.hosts: ["ekl.test.com:9300"]
                transport.host: ekl1.test1.com






                share|improve this answer













                share|improve this answer




                share|improve this answer










                answered Mar 28 at 23:43









                MilisterMilister

                3171 silver badge18 bronze badges




                3171 silver badge18 bronze badges

































                    draft saved

                    draft discarded















































                    Thanks for contributing an answer to Stack Overflow!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid


                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.

                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function ()
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55407015%2fnot-enough-master-nodes-discovered-during-pinging-elasticsearch-cluster-self-s%23new-answer', 'question_page');

                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown









                    Popular posts from this blog

                    Obelisk of Theodosius Contents History Description Notes Bibliography Further reading External links Navigation menuAge of spirituality : late antique and early Christian art, third to seventh centuryOver 60 picturesObelisks of the World41°00′21.24″N 28°58′31.43″E / 41.0059000°N 28.9753972°E / 41.0059000; 28.97539727724550-7235741376235741376

                    밀양 대씨 역사 각주 함께 보기 둘러보기 메뉴밀양 대씨

                    1973년 목차 사건 문화 탄생 사망 노벨상 달력 둘러보기 메뉴