Hi!
I'm gathering 5.6 options that are not present in 10.0 and the way we want to
handle them. Could you check options listed below and if you're aware of their
destiny indicate if options:
* not used or needed in MariaDB
* to be implemented in later 10.x versions
* tuned via different 10.x
On Fri, Nov 15, 2013 at 12:07:38PM +0400, Sergey Vojtovich wrote:
Hi!
I'm gathering 5.6 options that are not present in 10.0 and the way we want to
handle them. Could you check options listed below and if you're aware of their
destiny indicate if options:
* not used or needed in MariaDB
*
On 2013-11-15 07:32, Pavel Ivanov wrote:
Semi-sync replication for us is a DBA tool that helps to achieve
durability of transactions in the world where MySQL doesn't do any
flushes to disk. As you may guess by removing disk flushes we can
achieve a very high transaction throughput. Plus if we
Hi Kristian,
Thanks for the explanation. Let me elaborate a bit about the questions:
* how many workers are used: I know how many workers I have *enabled* by
@@slave_parallel_threads. But how many are really used? I see in
mysql.gtid_slave_pos that the number of rows grows and shrinks while the
Sergey Vojtovich s...@mariadb.org writes:
* binlog-max-flush-queue-time
This is not needed (it is about MySQL 5.6 group commit, MariaDB uses a
different implementation. I suppose one could say it is always set to 0).
* binlog-row-image
This is not merged to 10.0 yet (as far as I know). It
useful to have in I_S or P_S. I vote for I_S. P_S may be disabled by
admin due to its memory and cpu overhead.
-- Peter
-- Webyog
On Fri, Nov 15, 2013 at 11:20 AM, Kristian Nielsen kniel...@knielsen-hq.org
wrote:
Giuseppe Maxia g.ma...@gmail.com writes:
* which database they are running
Kristian,
Thanks for taking action with this issue. Another nice touch would be having
the default value of slave_parallel_threads=1 instead of 0, and doing the right
thing, as explained in this article:
http://datacharmer.blogspot.it/2013/11/parallel-replication-off-by-one.html
Cheers
Hi,
I think it makes sense to have it this way as its consistent with other
options in MySQL/MariaDB which makes it easier to check/bench the
overhead of a function.
Its also usually noted on the documentation that using this parameter is
not recommanded on a normal usecase (eg.
Sergei,
thanks for your feedback.
On Fri, Nov 15, 2013 at 12:32:11PM +0400, Sergei Petrunia wrote:
On Fri, Nov 15, 2013 at 12:07:38PM +0400, Sergey Vojtovich wrote:
Hi!
I'm gathering 5.6 options that are not present in 10.0 and the way we want
to
handle them. Could you check options
Hi Kristian,
thanks for your feedback it helped a lot. I updated jira task accordingly.
Below are fields that haven't been identified yet. And a few comments inline.
The following options exist in 5.6 but not in 10.0:
* default-tmp-storage-engine
* log-raw
* default-authentication-plugin
*
Sergey Vojtovich s...@mariadb.org writes:
* enforce-gtid-consistency
* gtid-mode
This is for MySQL 5.6 GTID, which will not be in MariaDB (we have a
completely
different GTID implementation). So they should not be implemented, nor should
we have dummy options for compatibility.
You
On Fri, Nov 15, 2013 at 03:53:47PM +0400, Sergey Vojtovich wrote:
Sergei,
thanks for your feedback.
On Fri, Nov 15, 2013 at 12:32:11PM +0400, Sergei Petrunia wrote:
On Fri, Nov 15, 2013 at 12:07:38PM +0400, Sergey Vojtovich wrote:
Hi!
I'm gathering 5.6 options that are not
12 matches
Mail list logo
