02-27-2013 11:09 AM
We gave a couple remote users access to the Campaigns. This has caused our application to send out hundreds of thousands of transactions to remote users (not just those two, but that is not important to me right now). The files are mainly history, campaigns, campaign targets, etc. This is choking our Sync process. It is still processing files from 2/19, over a week ago.
Users are getting individual sync files in the range of 150 to 350 MB. The only reason they are getting any files is because we moved all the waiting WGLog files out of the directory except for 3 or 4 so that it could process those and then complete the sync cycle pulling in inbound files and sending what it has. It is taking about 30 minutes to process each WGLog file which are about 10kb in size and have maybe 3 or 4 simple sql updates in them.
The transactions in the large TEF’s being sent to the users are NOT coming from WGLog. If I looked at all of the files there now, there would be a total of maybe 20,000 transactions. The WGLog directory seems to get only updates from the SLX UI. It seems that things that the SLX Server decides on its own need to be sent to remote users are “stored” somewhere else. What I’d like to do is just kill the whole decision from the SLX server to send the users these records. Since they are not in TEFs yet, killing this shouldn’t affect the existing and building WGLog files.
I just don’t know where this is all happening. It *seems* like I should be able to do something like Shut down sync, clear the temp files/ memory/ ??? of whatever it thinks it needs to send still, reboot the SLX and Sync Servers, and turn sync back on. The WGLogs should then continue to be picked up where they left off without the Sync Service pulling in this other data.
Anyone have any idea on how this bit works? Where the heck are those files or instructions to send them are stored or coming from?
02-27-2013 12:08 PM