CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site
This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using Core CiviCRM Functions (Moderator: Yashodha Chaku) »
  • Dedupe queries hanging in mySQL
Pages: [1]

Author Topic: Dedupe queries hanging in mySQL  (Read 595 times)

dschafer

  • I post occasionally
  • **
  • Posts: 93
  • Karma: 3
    • Backoffice Thinking
  • CiviCRM version: 3.2.3 - 4.4.4
  • CMS version: Drupal 6.x, 7.x, Wordpress
  • MySQL version: 5.1.x - 5.5.x
  • PHP version: 5.2.x - 5.4.x
Dedupe queries hanging in mySQL
May 29, 2012, 01:27:03 pm
Hi
We have this issue with a client install and have not been able to work around it.

If any type of transaction is performed the involves the temporary dedupe table MySQL, the query always ends up hanging in the "Copying to temp table..." state.

The client is running 3.3.5 and has 150K+ contacts.

We tried creating a new 4.1.1 instance with just the contact data loaded and ran a dedupe on first and last name and got the same result.

Looking around in MySQL seems like this is a long standing issue that queries can get stuck in this state.

Has anyone else encountered this in Civi?  Anyone find a solution? 

Searched the forums here but it was hard to find anything similar.

Became really disheartened when the problem occurred in 4.1.1

Thanks

Donald Lobo

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 15963
  • Karma: 470
    • CiviCRM site
  • CiviCRM version: 4.2+
  • CMS version: Drupal 7, Joomla 2.5+
  • MySQL version: 5.5.x
  • PHP version: 5.4.x
Re: Dedupe queries hanging in mySQL
May 30, 2012, 05:51:02 am


you can use dedupe hooks to optimize and write client specific dupe queries. NYSS has used this really nicely and has no dupe scaling issue (with DB's larger than the below)

4.1 has optimized the default queries a fair bit by hardcoding them via SQL queries (similar to the dedupe hook idea). If you can suggest ways on improving it, that would be great

lobo
A new CiviCRM Q&A resource needs YOUR help to get started. Visit our StackExchange proposed site, sign up and vote on 5 questions
Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using Core CiviCRM Functions (Moderator: Yashodha Chaku) »
  • Dedupe queries hanging in mySQL

This forum was archived on 2017-11-26.