I'm afraid this is one looks like a dreaded concurrency issue with the way we use file system as db in a farming environment. I would like you to make sure these registry parameters are set on each host and server hold the FFAStrans installation:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters]
"DirectoryCacheLifetime"=dword:00000000
"FileNotFoundCacheLifetime"=dword:00000000
"FileInfoCacheLifetime"=dword:00000000
I investigated into these things years ago and they seem to be helping these kind of issues. In theory, they might also help with the stuck monitor files...and all db concurrency in general. If these values miss in you registry just add them. They are well documented online: https://learn.microsoft.com/en-us/windo ... le-server/
admin wrote: ↑Wed Nov 27, 2024 6:32 pm
Hi DCCentR,
I'm afraid this is one looks like a dreaded concurrency issue with the way we use file system as db in a farming environment. I would like you to make sure these registry parameters are set on each host and server hold the FFAStrans installation:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters]
"DirectoryCacheLifetime"=dword:00000000
"FileNotFoundCacheLifetime"=dword:00000000
"FileInfoCacheLifetime"=dword:00000000
I investigated into these things years ago and they seem to be helping these kind of issues. In theory, they might also help with the stuck monitor files...and all db concurrency in general. If these values miss in you registry just add them. They are well documented online: https://learn.microsoft.com/en-us/windo ... le-server/
-steinar
Thanks, I added those registry keys, I just need to find a moment to reboot the servers.
I'm not quite clear, do you mean this is meant to be the solution for my “Got error code 6” error or is it meant to solve the execution of subsequent processors when getting an error in the previous one?
emcodem wrote: ↑Thu Nov 28, 2024 1:02 am
that webint dark skin looks just awesome, i play with the thought about making it default or even dump support for light skin in near future
Yeah, it's cool Have you thought about turning on “Row Colors” by default? When I didn't see the highlighted red error lines I was a little confused
DCCentR wrote: ↑Mon Dec 02, 2024 10:16 am
Have you thought about turning on “Row Colors” by default?
We have row colors?
That one is an ever going topic, one year its default, the other it is not working at all, next year it is default off
I think it makes sense to turn row colors on by default, just as the dark mode should be on by default, but who am i to decide that
I'm not quite clear, do you mean this is meant to be the solution for my “Got error code 6” error or is it meant to solve the execution of subsequent processors when getting an error in the previous one?
No, it's about making sure all i/o to the db folder is without any caching. This should will help concurrency issues. Other side effect of changing these registries can probably vary from system to system, and it might help other "strange" issues...but that's not the main reason. Turning of cache is normally never bad...as caching is after all cheating