Hi
> If memory serves me, the first timestamp, will be set
> to current universal time. Like db.table.last_changed
Ok, I replaced NOW() with a generated timestamp to avoid that NOW() deadlock.
sub mysql_now() {
my($sec,$min,$hour,$mday,$mon,$year,$wday, $yday,
$isdst)=localtime(time);
Hello dear fellow mariadb / gallera users.
It looks like I now found out what causes the deadlock. It's not the statement
NOW() and also not the concat statement (that might be a performance issue,
but we don't have that issue at the moment :-) )
I changed my 'update' script, to retry the trans
Hi,
To be able to help you more I need additional information, I
assume that you do not have autocommit=1, but could
you share show create table user ?
R: Jan
Hello dear fellow mariadb / gallera users.
It looks like I now found out w
Hi Jan
> To be able to help you more I need additional information, I assume that
> you do not have autocommit=1, but could
> you share show create table user ?
I did not set any autocommit statements. So I assume it's 1 as per default.
Sure:
CREATE TABLE `user` (
`id` int(11) NOT NULL AUTO_I
Hi,
I do not follow why you get deadlock is autocommit is not off. Is
this Galera ?
R: Jan
Hi Jan
To be able to help you more I need additional information, I assume that
you do not have autocommit=1, but could
you share sh
Hi
Thanks for your quick replies btw.
> I do not follow why you get deadlock is autocommit is not off. Is this
> Galera ?
Yes
Benoit Panizzon
--
I m p r o W a r e A G-
__
Zurlindenstrasse 29 Tel +41 61 826 93 07
CH-413
Hello
For those with the same problem, I found a completely stupid solution, which
works!
update user set lastlogin = IF(lastlogin != NOW(),NOW(),NOW()) where
concat(userid,'@',domain)='$USER'
For those now knowing what IF does...
If lastlogin is not NOW() update it and set it to NOW() else s
Hi,
Remember that in Galera, replication beats write locks. If you want to
avoid the deadlock ensure that updates to the table happen from only one
node, otherwise you simply have to retry the transaction. this is the case
with Galera or regular innodb. Your application must be able to handle
d
I would suggest turning on the InnoDB lock monitor (or at least look at the
ratio of locks held vs redo entries in SHOW ENGINE INNODB STATUS) to see
what locks the UPDATE is holding.
--Justin
On Thu, Dec 19, 2013 at 8:07 AM, Benoit Panizzon wrote:
> Hello
>
> For those with the same problem, I
Hello,
A new question has been asked in "Miscellaneous Functions" by ymhuang0808:
Hello!
My MariaDB version is 10.0.6. I found it dosen't support some MySQL 5.6
functions, like INET6_ATON(), INET6_NTOA(), IS_IPV4(), etc. Hope new version
MaraiDB support those fu
Hi,
Could you please describe you galera setup, MySQL and galera
versions, and how many nodes and configuration of the nodes. I
could not repeat your problem using 2-node galera cluster as seen
below:
jan@jan-GE70-0NC-0ND ~/mysql/galera-5.5 $
11 matches
Mail list logo
