TransportClient and NodeClient version tolerance


(Lukáš Vlček) #1

Hi,

may be a stupid question but is there any official statement/suggestion
about how much cluster ES version and ES TransportClient version can differ?
For example what is the risk of using ES 0.17.2 TransportClient against
0.17.4 cluster nodes? Is NodeClient more strict regarding version of ES of
the cluster it joins or does it also allow for some tolerance?

To make it clear I understand that in a long run it is recommended to have
all components in sync but speaking about short time intervals (for example
during upgrades) is there any safe version number interval in which
client(s) and cluster can differ and are guarantied to work ok?

Regards,
Lukas


(Shay Banon) #2

minor version releases are guaranteed to work "between them".

On Wed, Aug 10, 2011 at 1:42 PM, Lukáš Vlček lukas.vlcek@gmail.com wrote:

Hi,

may be a stupid question but is there any official statement/suggestion
about how much cluster ES version and ES TransportClient version can differ?
For example what is the risk of using ES 0.17.2 TransportClient against
0.17.4 cluster nodes? Is NodeClient more strict regarding version of ES of
the cluster it joins or does it also allow for some tolerance?

To make it clear I understand that in a long run it is recommended to have
all components in sync but speaking about short time intervals (for example
during upgrades) is there any safe version number interval in which
client(s) and cluster can differ and are guarantied to work ok?

Regards,
Lukas


(Lukáš Vlček) #3

Good to know!

On Wed, Aug 10, 2011 at 1:14 PM, Shay Banon kimchy@gmail.com wrote:

minor version releases are guaranteed to work "between them".

On Wed, Aug 10, 2011 at 1:42 PM, Lukáš Vlček lukas.vlcek@gmail.comwrote:

Hi,

may be a stupid question but is there any official statement/suggestion
about how much cluster ES version and ES TransportClient version can differ?
For example what is the risk of using ES 0.17.2 TransportClient against
0.17.4 cluster nodes? Is NodeClient more strict regarding version of ES of
the cluster it joins or does it also allow for some tolerance?

To make it clear I understand that in a long run it is recommended to have
all components in sync but speaking about short time intervals (for example
during upgrades) is there any safe version number interval in which
client(s) and cluster can differ and are guarantied to work ok?

Regards,
Lukas


(system) #4