Re: Cluster clients

[Nikolas Everett]

The only thing to keep in mind is that if the node is down you should just
retry on another one.  The client might handle that for you, I dunno.  its
important though because you don't want to lose 1/4 of your traffic when
you restart a node.

Nik

On Thu, Dec 11, 2014 at 3:11 PM, Nick Canzoneri  wrote:

> Most (all?) of the official clients have connection pool support that will
> query the cluster status and round robin across all the nodes with client
> capability enabled.
>
> Here's the appropriate link to the python docs:
>
> http://elasticsearch-py.readthedocs.org/en/master/connection.html#connection-pool
>
> Cheers,
>
> On Thu, Dec 11, 2014 at 2:28 PM, Morten Guldager <
> morten.gulda...@gmail.com> wrote:
>
>> I have just started with elasticsearch, have setup a cluster with 4
>> data/master nodes. everything pretty default. The nodes are called E1, E2,
>> E3 and E4.
>>
>> I have implemented a few pieces of client software, and doing RESTful
>> communication against http://E1:9200/ is super easy.
>>
>> But how are the clients supposed to address the cluster? Pointing
>> directly to a specific cluster node seems not right, that particular node
>> might be down. Also, configuring all clients with knowledge about all
>> cluster nodes seems impractical too.
>>
>> Of cause I could setup old-school round robin DNS. Is that the way to do
>> it or do we have smarter options?
>>
>> Ah yes, I'm using python and the elasticsearch module. Everything is on
>> linux.
>>
>>
>> /mogul
>>
>> --
>> 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/8e0d2e30-dd34-4ee3-854e-52edece9b821%40googlegroups.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Nick Canzoneri
> Developer, Wildbit 
> Beanstalk , Postmark ,
> dploy.io
>
> --
> 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/CAKWm5yMbyDShtovep46rnVM7-NY3ABDYwz3m1HorPRORLTWk8w%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/CAPmjWd1HbiDmO_89Zqmh4ptT3XF5L3hbHVoQrODDv_vnZZwZhA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Cluster clients

[Nick Canzoneri]

Most (all?) of the official clients have connection pool support that will
query the cluster status and round robin across all the nodes with client
capability enabled.

Here's the appropriate link to the python docs:
http://elasticsearch-py.readthedocs.org/en/master/connection.html#connection-pool

Cheers,

On Thu, Dec 11, 2014 at 2:28 PM, Morten Guldager 
wrote:

> I have just started with elasticsearch, have setup a cluster with 4
> data/master nodes. everything pretty default. The nodes are called E1, E2,
> E3 and E4.
>
> I have implemented a few pieces of client software, and doing RESTful
> communication against http://E1:9200/ is super easy.
>
> But how are the clients supposed to address the cluster? Pointing directly
> to a specific cluster node seems not right, that particular node might be
> down. Also, configuring all clients with knowledge about all cluster nodes
> seems impractical too.
>
> Of cause I could setup old-school round robin DNS. Is that the way to do
> it or do we have smarter options?
>
> Ah yes, I'm using python and the elasticsearch module. Everything is on
> linux.
>
>
> /mogul
>
> --
> 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/8e0d2e30-dd34-4ee3-854e-52edece9b821%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Nick Canzoneri
Developer, Wildbit 
Beanstalk , Postmark ,
dploy.io

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

Cluster clients

[Morten Guldager]

I have just started with elasticsearch, have setup a cluster with 4 
data/master nodes. everything pretty default. The nodes are called E1, E2, 
E3 and E4.

I have implemented a few pieces of client software, and doing RESTful 
communication against http://E1:9200/ is super easy.

But how are the clients supposed to address the cluster? Pointing directly 
to a specific cluster node seems not right, that particular node might be 
down. Also, configuring all clients with knowledge about all cluster nodes 
seems impractical too.

Of cause I could setup old-school round robin DNS. Is that the way to do it 
or do we have smarter options?

Ah yes, I'm using python and the elasticsearch module. Everything is on 
linux.


/mogul

-- 
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/8e0d2e30-dd34-4ee3-854e-52edece9b821%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.