Buy Percona ServicesBuy Now!

Percona Server for MongoDB 3.6.4-1.2 Is Now Available

Lastest Forum Posts - May 24, 2018 - 6:12am
Percona announces the release ofPercona Server for MongoDB3.6.4-1.2 on May 23, 2018. Download the latest version from the Percona web site or the Percona Software Repositories.

Percona Server for MongoDB is an enhanced, open source, and highly-scalable database that is a fully-compatible, drop-in replacement for MongoDB 3.6 Community Edition. It supports MongoDB 3.6 protocols and drivers.

Percona Server for MongoDB extends MongoDB Community Edition functionality by including the Percona Memory Engine, as well as several enterprise-grade features. Percona Server for MongoDB requires no changes to MongoDB applications or code.

This release is based on MongoDB 3.6.4 and includes the following additional changes:
  • #PSMDB-205: mongod failed to initialize if audit filter was set to record Action type events specified with the $in expression.
  • #PSMDB-207: a premature initialization of the feature compatibility version in global parameters was fixed for the RocksDB storage engine.
  • #PSMDB-209: CentOS 6 and CentOS 7 RPM packages contained config file with a wrong link to the online Percona Memory Engine documentation.
Note: as mentioned in the Percona Server for MongoDB 3.6.3-1.1 Release Notes, MongoRocks is deprecated in Percona Server for MongoDB 3.6.

The Percona Server for MongoDB 3.6.4-1.2 release notes are available in the official documentation.

WSREP detected deadlock/conflict

Lastest Forum Posts - May 24, 2018 - 3:12am
I am getting WSREP detected deadlock/conflict with Percona latest version. I am using spring boot app to save my entity but some time this conflict occurs. It occurs at many places. Since I am testing I do not have much data but I hit database couple of times.
This is the log from node1 & node2
Code: 018-05-23T11:36:28.362290Z 127478 [Note] WSREP: --------- CONFLICT DETECTED -------- 2018-05-23T11:36:28.362338Z 127478 [Note] WSREP: cluster conflict due to certification failure for threads: 2018-05-23T11:36:28.362348Z 127478 [Note] WSREP: Victim thread: THD: 127478, mode: local, state: executing, conflict: cert failure, seqno: 2381 SQL: commit This is the exception from spring boot app
Code: org.springframework.orm.jpa.JpaSystemException: com.mysql.jdbc.exceptions.jdbc4.MySQLTransactionRollbackException: WSREP detected deadlock/conflict and aborted the transaction. Try restarting the transaction; nested exception is javax.persistence.PersistenceException: com.mysql.jdbc.exceptions.jdbc4.MySQLTransactionRollbackException: WSREP detected deadlock/conflict and aborted the transaction. Try restarting the transaction at org.springframework.orm.jpa.EntityManagerFactoryUtils.convertJpaAccessExceptionIfPossible(EntityManagerFactoryUtils.java:418) at org.springframework.orm.jpa.DefaultJpaDialect.translateExceptionIfPossible(DefaultJpaDialect.java:122) at org.springframework.orm.jpa.JpaTransactionManager.doCommit(JpaTransactionManager.java:521) at org.springframework.transaction.support.AbstractPlatformTransactionManager.processCommit(AbstractPlatformTransactionManager.java:761) at org.springframework.transaction.support.AbstractPlatformTransactionManager.commit(AbstractPlatformTransactionManager.java:730) at org.springframework.transaction.interceptor.TransactionAspectSupport.commitTransactionAfterReturning(TransactionAspectSupport.java:504) at org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:292) at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:96) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) at org.springframework.dao.support.PersistenceExceptionTranslationInterceptor.invoke(PersistenceExceptionTranslationInterceptor.java:136) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) at org.springframework.data.jpa.repository.support.CrudMethodMetadataPostProcessor$CrudMethodMetadataPopulatingMethodInterceptor.invoke(CrudMethodMetadataPostProcessor.java:133) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:92) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) at org.springframework.data.repository.core.support.SurroundingTransactionDetectorMethodInterceptor.invoke(SurroundingTransactionDetectorMethodInterceptor.java:57) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:213) at com.sun.proxy.$Proxy153.save

The server quit without updating PID file (/var/lib/mysql/db-1.pid) [fail]

Lastest Forum Posts - May 24, 2018 - 2:52am
Hi All,

Anybody help..

I Can't start bootsrap-pxc.. error it's:
https://paste.fedoraproject.org/past...g2q83FDcsOrTDw

root@db-1:/etc/mysql/conf.d# /etc/init.d/bootmisc.sh status root@db-1:/etc/mysql/conf.d#


my error log:
https://paste.fedoraproject.org/past...pxSuVvPWoUYGpQ


Thank you,

riki

Querying Buffer Pool of InnoDB directly. Is it possible?

Lastest Forum Posts - May 24, 2018 - 1:00am
For us, it is very important to get high response time for our website php script which queries a large database. It is essentially getting user information for the user who visited the page. There may be millions of users in the db.

We would like to not bother using the user data at all if the record is not already in the InnoDB Buffer Pool of the MySQL database, and use information only if present in the above cache.

Is there a way to directly ask Mysql/InnoDB whether the record is in cache?
Visit Percona Store


General Inquiries

For general inquiries, please send us your question and someone will contact you.