This is a frustration that has gone on for years. Tech support's help hasn't solved, so I'm posting here to see if others have the same problem.
Background: I have 140,000 indexed files. But many other files (200 to 300 mb) will not index, but they are in folders that have indexed files so I can't simply exclude a folder to avoid CDS tripping on them.
When I had a scheduled scanning/indexing it would take days for CDS to churn through them, which leads to problems of cascading schedules and never-ending indexing. I have just replaced my worn out hard drive, and I'm sure constant indexing by CDS contributed a lot to the failure.
Support's proposed solution: (1) Disable all scheduling, and (2) close CDS and delete all of the files in the queue (in my case F:\CDS-Index\index\queue\MainChunk\*.*.
Result: CDS appears to start in an idle mode. After an hour or two it starts scanning my drive, even though I have a complete index already and all scheduling disabled. (It skips over all of the already indexed files and tries to index all the ones it could never index before.) So the problem continues unchanged - and I have tried this method multiple times in recent years, as well as again today.
The continuing problem: There is apparently no way to make CDS start indexing cycle only on user demand only, manually (apart from files and folders it sees as being changed in real time). It does not respect the disabling of all scheduling choices.
Screen shots attached: (1) I happened to catch the end of one indexing cycle this morning. Two newly generated files were indexed, the a NEW indexing cycle began. (2) My indexing performance setting - everything disabled (even down the list). There is no option to avoid the "Perform daily scheduled tasks at (time)" - which may be part of the problem. (3) My advanced settings. (4) The main chuck folder at 14:28 this afternoon, shortly after a new indexing cycle started automatically. (5) Changes in that folder about an hour later.
Conclusion: Something needs to be fixed in the program.
This is a frustration that has gone on for years. Tech support's help hasn't solved, so I'm posting here to see if others have the same problem.
Background: I have 140,000 indexed files. But many other files (200 to 300 mb) will not index, but they are in folders that have indexed files so I can't simply exclude a folder to avoid CDS tripping on them.
When I had a scheduled scanning/indexing it would take days for CDS to churn through them, which leads to problems of cascading schedules and never-ending indexing. I have just replaced my worn out hard drive, and I'm sure constant indexing by CDS contributed a lot to the failure.
Support's proposed solution: (1) Disable all scheduling, and (2) close CDS and delete all of the files in the queue (in my case F:\CDS-Index\index\queue\MainChunk\*.*.
Result: CDS appears to start in an idle mode. After an hour or two it starts scanning my drive, even though I have a complete index already and all scheduling disabled. (It skips over all of the already indexed files and tries to index all the ones it could never index before.) So the problem continues unchanged - and I have tried this method multiple times in recent years, as well as again today.
The continuing problem: There is apparently no way to make CDS start indexing cycle only on user demand only, manually (apart from files and folders it sees as being changed in real time). It does not respect the disabling of all scheduling choices.
Screen shots attached: (1) I happened to catch the end of one indexing cycle this morning. Two newly generated files were indexed, the a NEW indexing cycle began. (2) My indexing performance setting - everything disabled (even down the list). There is no option to avoid the "Perform daily scheduled tasks at (time)" - which may be part of the problem. (3) My advanced settings. (4) The main chuck folder at 14:28 this afternoon, shortly after a new indexing cycle started automatically. (5) Changes in that folder about an hour later.
Conclusion: Something needs to be fixed in the program.
Attachments (5)
1 - CDS problem - the end of one indexing and start of a new one.png
192 KB
2 - CDS Indexing Performance settings - Screenshot.png
128 KB
3 - CDS - Advanced settings screenshot.png
146 KB
4 - CDS_2C New queue automatically establishedScreenshot at 14-28 hours.png
138 KB
5 - CDS_2C New queue automatically establishedScreenshot at 15-34 hours.png
131 KB
0 Votes
0 Comments
Login or Sign up to post a comment