codership/galera documentation wiki?

22 views
Skip to first unread message

Maarten van Baarsel

unread,
May 7, 2013, 6:33:08 PM5/7/13
to percona-d...@googlegroups.com
Is it relevant for PXC or should I just forget it exists?

http://www.codership.com/wiki/

(I was wondering about wsrep_local_cache_size)

thanks,
M.

Alex Yurchenko

unread,
May 7, 2013, 7:03:31 PM5/7/13
to percona-d...@googlegroups.com
On 2013-05-08 01:33, Maarten van Baarsel wrote:
> Is it relevant for PXC or should I just forget it exists?
>
> http://www.codership.com/wiki/

It is pretty much the same as with code. They take our patch and port
it to their code, potentially making own changes. I'm not sure it is up
to us to say that you should forget it exists. But perhaps it is up to
Percona if they feel that theirs is more adequate.

> (I was wondering about wsrep_local_cache_size)

Oh, this was deprecated years ago. Fixed. Thanks.

> thanks,
> M.

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

Raghavendra D Prabhu

unread,
May 7, 2013, 9:04:52 PM5/7/13
to percona-d...@googlegroups.com
Hi ,
>--
>You received this message because you are subscribed to the Google Groups "Percona Discussion" group.
>To unsubscribe from this group and stop receiving emails from it, send an email to percona-discuss...@googlegroups.com.
>To post to this group, send email to percona-d...@googlegroups.com.
>For more options, visit https://groups.google.com/groups/opt_out.
>
>
As Alexey mentioned, it is relevant for PXC. If you see any
discrepancy between the two, you may want to report a
documentation bug with us.




Regards,
--
Raghavendra Prabhu
Percona LLC. - http://www.percona.com / Blog: http://www.mysqlperformanceblog.com/
Skype: percona.raghavendrap
GPG: 0xD72BE977
Contact: http://wnohang.net/contact

Make plans to attend Percona Live London MySQL Conference
2013.<http://www.percona.com/live/london-2013/>

Maarten van Baarsel

unread,
May 8, 2013, 7:31:54 AM5/8/13
to percona-d...@googlegroups.com
On 08-05-2013 01:03:31, Alex Yurchenko wrote:
> On 2013-05-08 01:33, Maarten van Baarsel wrote:
>> Is it relevant for PXC or should I just forget it exists?
>>
>> http://www.codership.com/wiki/
>
> It is pretty much the same as with code. They take our patch and port it to
> their code, potentially making own changes. I'm not sure it is up to us to say
> that you should forget it exists. But perhaps it is up to Percona if they feel
> that theirs is more adequate.

I had no intention to insult anyone, I apologize profusely if I did so.

It's just that PXC talks about Galera 2.x and I cannot seem to find a mention
to that in the codership wiki, at all. So I was confused.

(which one should I read for PXC:

http://www.codership.com/wiki/doku.php?id=galera_parameters or
http://www.codership.com/wiki/doku.php?id=galera_parameters_0.8
? 0.8 is more prominent on http://www.codership.com/wiki/doku.php?id=info)


It's just that I sometimes see "mandatory" things in Percona blogposts [2],[1]
that are new to me (having read the wiki) so I was wondering what the
definitive manual was. But I see now that the wiki has been extended a lot
since I've read it last, thanks.


Are there, besides the ones mentioned on
http://www.codership.com/wiki/doku.php?id=monitoring , variables that are
useful/important to graph? I'm writing a munin plugin to monitor the
replication status (hence my digging in the docs).

M.

[1]
http://www.mysqlperformanceblog.com/2013/05/02/galera-flow-control-in-percona-xtradb-cluster-for-mysql/
(first thought: "flow control, huh?")

[2]
http://www.mysqlperformanceblog.com/2013/05/01/follow-these-basics-when-migrating-to-percona-xtradb-cluster-for-mysql/
(first thought: "log_slave_updates required?")

Alex Yurchenko

unread,
May 8, 2013, 11:25:17 AM5/8/13
to percona-d...@googlegroups.com
On 2013-05-08 14:31, Maarten van Baarsel wrote:
> On 08-05-2013 01:03:31, Alex Yurchenko wrote:
>> On 2013-05-08 01:33, Maarten van Baarsel wrote:
>>> Is it relevant for PXC or should I just forget it exists?
>>>
>>> http://www.codership.com/wiki/
>>
>> It is pretty much the same as with code. They take our patch and port
>> it to
>> their code, potentially making own changes. I'm not sure it is up to
>> us to say
>> that you should forget it exists. But perhaps it is up to Percona if
>> they feel
>> that theirs is more adequate.
>
> I had no intention to insult anyone, I apologize profusely if I did
> so.

By god, I just pointed out the proper authority there. It is for
Percona to decide whether information in Codership's wiki is no longer
relevant to their product.

What we can be certain about is that Percona aims to make their
documentation no less (and at times more) comprehensive than our wiki.
So it is unlikely that you will find any revelations in our wiki. But,
naturally, all new features are described here first.

> It's just that PXC talks about Galera 2.x and I cannot seem to find a
> mention
> to that in the codership wiki, at all. So I was confused.

User visible Galera behaviour changed only incrementally since 0.7
release, so there was no pressing need to rewrite everything for 2.x.
PXC pretty much started with 2.x.
Oops, that page didn't see much maintenance in years. Thanks for
pointing that out. Did some ad-hoc hack'n'slashing,
galera_parameters_0.8 is no more. But it is still a mess.

> It's just that I sometimes see "mandatory" things in Percona blogposts
> [2],[1]
> that are new to me (having read the wiki) so I was wondering what the
> definitive manual was. But I see now that the wiki has been extended a
> lot
> since I've read it last, thanks.

Percona posts are likely to be more comprehensive than simple
reference, and reflect recommended practice. They may contain some
errors as well, but normally those are ironed out.

> Are there, besides the ones mentioned on
> http://www.codership.com/wiki/doku.php?id=monitoring , variables that
> are
> useful/important to graph? I'm writing a munin plugin to monitor the
> replication status (hence my digging in the docs).

Hardly. The rest are mostly for debugging.
Reply all
Reply to author
Forward
0 new messages