Proget Filewatcher

Hi guys,

we get this error

Package Indexing Error
Feed	Test
Package	Test.1.0.0.nupkg
Message	The process cannot access the file 'D:\Data\Test\Test.1.0.0.nupkg' because it is being used by another process.
Date	7/16/2014 4:04:46 PM
Stack Trace	 at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share)
at Inedo.NuGet.Packages.NuGetPackage.ReadFromNupkgFile(String fileName)
at Inedo.ProGet.Extensibility.PackageStores.DirectoryPackageStore.TryReadPackage(String fileName)

and we see in the process list Proget service runs 4 times and only read packages and can't add new one. If you try to add a new package you get the "Package Indexing Error". Please check the Filewatcher and make him faster and make him write new stuff in the same time he reads packages.

Our environment:

Windows 2012 R2

Total packages: 20000 piece => 90GB total amount

Product: ProGet
Version: 3.1.0

Hi Philipp, this error should go away on its own the next time the indexer is run; it runs every 60 seconds by default.

hi
yes the error goes away it takes about 60~ minutes so long needed the file watcher to for 20000 package to check and then he can only add new ones.

there's a possibility to improve it?

We can add a configurable throttle to the timer that triggers a package rescan. In the meantime, you can always trigger an immediate index rebuild by either setting the RebuildPackageIndex setting (under Admin->All Settings) to True, or by restarting the ProGet service.