CiviCRM Community Forums (archive)

I am using drupal 6.20 and CiviCRM 3.3.2.

I have an installation of drupal with 26,200 users in the user table.  When I click to 'Synchronize Users to Contacts' (http://netsquared.org/civicrm/admin/synchUser?reset=1) and click okay, the process always ends in an error usually related to memory allocation (even after increasing the memory limit to 192M) - usually a timeout kind of thing after about 10minutes. 

What I notice is that although it times out on the browser, the database is still performing the opperations (the number of entries in the civicrm_uf_match table fluctuates for a while afterwards).

Once it stabilizes (I've done this a few times) it gives a different end number in the civicrm_uf_match table:
20,126
19,994
19,468
20,086

Once that table stabilizes, it has never had the same amount of entries as is in the users (drupal) table.

Can you help me understand if/how these errors/discrepancies are occurring and if there is a need to do anything about them?  Is there any documentation that I can read that explains what is going on and might give me insight in how to address it? 

Thanks!

I completely REMOVED CiviCRM and started from scratch, and as soon as I fill the civicrm_uf_match table, it starts growing and shrinking again. 

Is this supposed to happen?  It isn't happening on any of my smaller CiviCRM installations...

Here is the saga that I tried before conceding to starting from scratch: (from an internal post)
the question i am asking myself is what is it going to take to kill the beast. here is the chronicle of my final (and i think somewhat heroic) effort to kill this process without having to completely reinstall civicrm:

1) with the same conditions as described in my last comment below (civicrm modules folder renamed, CMSUser.php changes as per the civi-forum mentioned below, run cron and clear all caches again, set php execution_limit via .htaccess file to 3600, rebooted mysql server, etc, etc)

2) i remove the civicrm_uf_match table completely from the database (after backing it up, of course) for 15 hours (54000 seconds).

3) when i reload that table, i begin checking the numbers in that table, and immediately they start fluctuating again.

short of a conversation with someone at civi who will pay attention to my ticket/s on their forums, i am not sure what to do. i have spoken with philip as well (who came up with the forum link below that i used to change the CMSUser.php file), and i am curious what he would think at this point.

hey lobo, thanks for your response.  i actually, as i said in my last entry, did do it in small batches (according to the link above), and the synching part itself went great.  the issue is that there might have been old processes that were still alive from the first time we tried. 

i am gatherring from your respoinse that this civicrm_uf_matches table is indeed not supposed to continually fluctuate.  any ideas how to destroy old processes from my first try that are not seeming to have died?  at this point, i completely removed and reinstalled civicrm on both machines.  the interesting part to me is that this last time, i only ran the synching in dev, and then copied that database over after doing a very simple installation (without configuring anything) on production. 

The point being that the new civicrm_uf_match table in production is fluctuating as well.   I never actually ran the synching in production this time around (instead i did it in dev and then copied the database over) so I am assuming that these are old processes that still have not died.

Any ideas?