Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
codership
Home
+ new post
About this group
Join this group
Message from discussion Galera 2.2
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Henrik Ingo  
View profile  
 More options Nov 1 2012, 7:56 am
From: Henrik Ingo <henrik.i...@avoinelama.fi>
Date: Thu, 1 Nov 2012 13:56:05 +0200
Local: Thurs, Nov 1 2012 7:56 am
Subject: Re: [codership-team] Galera 2.2
Print | View thread | Show original | Report this message | Find messages by this author
On Thu, Nov 1, 2012 at 12:01 AM, Alex Yurchenko

<alexey.yurche...@codership.com> wrote:
>> that are currently members of the cluster (current cluster
>> configuration), and therefore traffic in the form of galera protocol
>> is expected and accepted.

> No. It is about where MySQL client connections are expected and accepted.

>> Or would it also contain addresses specified in wsrep_cluster_address,
>> even if those nodes haven't actually shown up yet?

> Only the members of component.

>> Let me ask another question which you can answer more easily: Kind of
>> a FAQ is "how can I find out which nodes are currently connected to
>> the cluster?" Is this the variable that answers that question?

> Well, this list should be it if you can identify the nodes by the addresses
> where they listen for client connections at. (again the same construction
> which I believe is sufficiently grammatically correct and unambiguous, yet
> so easy to misunderstand)

Thanks, it makes sense now!

I have run Galera clusters where MySQL listens for client connections
on one network interface and Galera replication happens on another
interface. So I was focused on wsrep variables only being concerned
with the Galera replication. But like before, what you did here is a
very useful and user friendly piece of information and exceeded what
my imagination could expect. Good work!

In addition to knowing which nodes are currently part of the primary
cluster component, this information is directly usable as a list of
addresses that clients can use to connect to cluster. Very useful!

henrik

>> henrik

>>> On 2012-10-30 13:48, Henrik Ingo wrote:

>>>> Alex, what do you mean with "client" in this one:

>>>>> wsrep_incoming_addresses status variable contains a comma-separated
>>>>> list
>>>>> of
>>>>> incoming (client) addresses in the cluster component

>>>> Since I can see incoming client addresses with SHOW PROCESSLIST, I'm
>>>> thinking this is something Galera related?

>>>> henrik

>>>> On Mon, Oct 29, 2012 at 3:30 PM, Alexey Yurchenko
>>>> <alexey.yurche...@codership.com> wrote:

>>>>> Sorry guys, just didn't want to duplicate what has been already written
>>>>> here. But I guess you're right:

>>>>> Fixed:

>>>>> causal reads guarantee violation at cluster partitioning
>>>>> exclusive keys didn't produce dependency on shared keys
>>>>> race condition in desync method (could break RSU)
>>>>> IST was not working across different EC2 accessibility zones (and
>>>>> similar)
>>>>> causal reads timeout configuration was ignored

>>>>> Added:

>>>>> wsrep_incoming_addresses status variable contains a comma-separated
>>>>> list
>>>>> of
>>>>> incoming (client) addresses in the cluster component
>>>>> ability to specify several node addresses in gcomm:// URL.

>>>>> Performance:

>>>>> Significant speedups and memory footprint reduction on ranged queries.

>>>>> Regards,
>>>>> Alex

>>>>> On Monday, October 29, 2012 11:54:20 AM UTC+2, Thomas Linnemann wrote:

>>>>>> Am 29.10.2012 03:38, schrieb Vadim Tkachenko:
>>>>>> > Alex,

>>>>>> > So, is there a detailed ChangeLog with all
>>>>>> > new features and bug fixed ?

>>>>>> Hi,
>>>>>> detailed changelog with new features would be nice.
>>>>>> Update from 23.2.1 runs very smooth.

>>>>>> thank you for galera

>>>>>> Thomas

>>>>> --

>>> --
>>> Alexey Yurchenko,
>>> Codership Oy, www.codership.com
>>> Skype: alexey.yurchenko, Phone: +358-400-516-011

>>> --

> --
> Alexey Yurchenko,
> Codership Oy, www.codership.com
> Skype: alexey.yurchenko, Phone: +358-400-516-011

> --

--
henrik.i...@avoinelama.fi
+358-40-8211286 skype: henrik.ingo irc: hingo
www.openlife.cc

My LinkedIn profile: http://www.linkedin.com/profile/view?id=9522559


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google