Hi all!
On 10/14/2016 11:10 AM, jocelyn fournier wrote:
Hi!
Regarding the TokuDB bugs, they are so far fixed quite quickly by
Percona.
I want to clarify the source of the question (FUD) about Percona not
fixing TokuDB bugs, and hopefully bring it to an end. It apparently
comes from me,
I didn't expect that autocommit = OFF will affect the replication feature.
I thought replication will be handled irrespective what commit type is
enabled in the DB Server.
So whenever I promote any new master from a slave, I have to taken care
this auto commit accordingly. Is my understanding
Is anyone surprised by the lack of TokuDB support? Percona is primarily an
Oracle MySQL fork . The InnoDB changes in MySQL 8 represent something
entirely different. Good, but different.
I don't think I am being too speculative when I say, I am sure Oracle are
in no hurry to make MySQL a serious
I don't think (most) guys must migrate from other RDBM, normally they
select mysql/mariadb/webscale/etcetc before starting the project, a
migration "in the middle" of a project is costly.
I agree, there's many open issue at jira/mysql bug report/percona/etc/etc
and others issue tracker systems
Hi All,
I have the below topology:
Master -> Slave (using GTID replication)
Master -> Maxscale (Binlog Router)
Maxscale -> DR Site (via binlog router)
my.cnf is same across all sites:
lower-case-table-names=1
autocommit=0
#replication variables
log-bin=binlog
binlog-format=ROW
Karthick Subramanian writes:
> Below when I try at Slave DB:
>
> MariaDB [dr_repl]> select * from test_dr_repl;
> Empty set (0.00 sec)
>
> MariaDB [dr_repl]> commit;
> Query OK, 0 rows affected (0.00 sec)
>
> MariaDB [dr_repl]> select * from test_dr_repl;
>
Karthick:
You should post this in maxscale group as well.
Dipti
On Fri, Oct 14, 2016 at 6:34 PM, Kristian Nielsen
wrote:
> Karthick Subramanian writes:
>
> > Below when I try at Slave DB:
> >
> > MariaDB [dr_repl]> select * from
Am 14.10.2016 um 15:21 schrieb Richard Bensley:
Me and many others had hope that TokuDB would be the death of InnoDB in
MariaDB, and the catalyst to a truly amazing open source database.
please fix that "many others" above by saying "some others" - if we
would like a "truly amazing open
>
> On Friday, 14 October 2016, Roberto Spadim wrote:
>
>> I don't think (most) guys must migrate from other RDBM, normally they
>> select mysql/mariadb/webscale/etcetc before starting the project, a
>> migration "in the middle" of a project is costly.
>> I agree, there's
i read opnions about why choose mysql, and the common point is 'mysql runs
simple queries really fast' i think that's the main feature of mysql
2016-10-14 11:25 GMT-03:00 Reindl Harald :
>
>
> Am 14.10.2016 um 15:21 schrieb Richard Bensley:
>
>> Me and many others had
Can you describe your schema and typical queries please?
Sent from my iPhone
> On Oct 14, 2016, at 12:33 PM, Jon Foster wrote:
>
> I have a DB scenario that is very write intensive. Essentially its a
> large scale hit counter of sorts. Currently we're running on a
Excerpts from Jon Foster's message of 2016-10-14 09:33:59 -0700:
> I have a DB scenario that is very write intensive. Essentially its a
> large scale hit counter of sorts. Currently we're running on a single
> 12core server with 6 SSDs in a RAID6 array. But we're looking for a way
> to scale out
I asked about schema and queries to determine which sharding framework makes
the most sense to suggest.
Sent from my iPhone
> On Oct 14, 2016, at 1:05 PM, Clint Byrum wrote:
>
> Excerpts from Jon Foster's message of 2016-10-14 09:33:59 -0700:
>> I have a DB scenario that is
I have a DB scenario that is very write intensive. Essentially its a
large scale hit counter of sorts. Currently we're running on a single
12core server with 6 SSDs in a RAID6 array. But we're looking for a way
to scale out write volume by adding more servers, hopefully as
conveniently as I might
Clint Byrum wrote:
Excerpts from Jon Foster's message of 2016-10-14 09:33:59 -0700:
I have a DB scenario that is very write intensive. Essentially its a
large scale hit counter of sorts. Currently we're running on a single
12core server with 6 SSDs in a RAID6 array. But we're
15 matches
Mail list logo