… not only for user-initiated XA, but also for internal XA coordination between the InnoDB transaction logs and the MySQL binary logs, to ensure… in XA transactions is enabled, which causes an extra disk flush for transaction preparation. If you do not wish to use XA transactions, you can disable…
Post: New SpecJAppServer results at MySQL and Sun.
November 12, 2008 By Leave a Comment
… the most interesting: MySQL 5.0 Tuning in /etc/my.cnf (included in FDA) [mysqld] sql-mode = IGNORE_SPACE transaction-isolation = READ…_support_xa=0 innodb_flush_method = O_DIRECT First the options are somethat benchmark optimized – for example doublewrite is disabled; checksums are disabled…
Post: Announcing Percona Server 5.5.27-29.0
October 11, 2012 By Leave a Comment
…binlog shouldn’t be rotated while it contains XA transactions in the PREPARED state. Bug fixed #1036040 (… When set to 0 (default), flashcache checks are disabled and when set to 1 checks are … maximum number of indexes per table. Upstream MySQL bugs: #54127, #61178, #61179 and #61180. Bug fixed…
Comment: Jeremy Cole on MySQL Replication
June 14, 2006 By 12 Comments
…-commit-and-xa), I read that entry with interest, and what I took from it was that you should disable xa-support in… MySQL 5.0; it was made obsolete by the introduction of XA transaction support.)” I’m not sure what to make of that. XA… you’re using MySQL 5, and it’s the only transactional resource you’re using, is it safe to DISABLE innodb_xa_support? i…
Post: MySQL 4 to MySQL 5 Upgrade performance regressions
June 6, 2007 By 8 Comments
… working code path if XA is disabled ? Many customers do not flush binary log anyway and use single transactional storage engine so they… concurrent transactions so group commit would trigger in MySQL 4.0 and large number of transactions in total so serializing them would make MySQL… should stay on MySQL 4.1 until MySQL has taken it away from you as already happened with MySQL 4.0. MySQL 5.0…
Comment: Jeremy Cole on MySQL Replication
June 17, 2006 By 12 Comments
…. In MySQL 5.0 you can disable innodb_xa_support and you can get binary log possibly out of sync with innodb transactional log. However it will not make group commit to work. Group commit only works in MySQL 5.0… is disabled at all. Take a look at these benchmarks: http://www.mysqlperformanceblog.com/2006/05/19/group-commit-and-xa/ – disabling XA saves…
Post: Heikki Tuuri Innodb answers - Part I
October 26, 2007 By 19 Comments
… typically enough. Q23: Rumor has it that if you disable the new XA support (which we don’t use) then you’ll… implement XA, and switching off the XA will not remove that serialization. MySQL‘s binlog and InnoDB’s log must have the transactions in the same order, for a recovery based on MySQL‘s…
Post: Comparing Percona XtraDB Cluster with Semi-Sync replication Cross-WAN
June 14, 2012 By 7 Comments
…I attribute this to log-bin and innodb_support_xa being disabled in the PXC environments Semi-sync performs dismally under…scale much further across high latency environments. If each transaction took 100ms to commit, then I’d expect … disaster recovery than semi-synchronous replication in stock MySQL…
Post: Group commit and real fsync
May 3, 2006 By 9 Comments
…. In the nutshell the problem is – new feature – XA was implemented in MySQL 5.0 which did not work with former group… trigered by enabled binary log. if binary log is disabled, so is XA and old group commit code works just fine. Second… will be much smaller, especially with large transactions. So how you can solve the problem ? Disable binary log. This could be option…
