LCP service is broken #515
Comments
|
The service is just really slow right now. Increasing LCP_MAX_DOWNLOAD_TRIES from 40 to 200 just worked for me. |
|
Hey Natalie, I modified landfireclient.cpp and increased LCP_MAX_DOWNLOAD_TRIES to 200 but it is still not working for us and I am unable to fetch the LCP elevation files. |
|
@rdwadhwani0220 Thanks for the update. Other users are reporting much longer download times as well. One user reported that |
|
@nwagenbrenner Sure, update me when you receive any solution. However, I increased to 5000 also but it failed to work for our case. |
|
The response from LANDFIRE: In the last several months, LFPS has been going through many changes. We are working to bolster and enhance LFPS, this has required some large changes in the background. We are aware of the increased processing time and are actively investigating the issue. Thank you for providing the details about your job, we hope to have the increased processing time issue resolved in the near future and we apologize for the inconvenience. Maybe a good time to work on #459. |
…o 300 in a partial attempt to make lcp downloads more likely to finish This will only be temporarily for while the LCP download service remains as crazy slow as it has been for the last two months. They're working on it, so hopefully it doesn't go on for too much longer. But as it stands, this is just a partial fix because sometimes the lcp downloads have been working in 200 to 300 attempts, and sometimes up to 1000 attempts, and sometimes 5000 attempts isn't enough. For reference, the default 40 attempts seems to take about 2 minutes, 100 attempts 5 minutes, 200 attempts 8 minutes, 300 attempts about 10 minutes. I tried 2000 attempts and then 5000 attempts on a really bad time period, and it took 1.5 hrs and up to 2.5 hrs or so respectively, way longer than any of the more computationally expensive WindNinja runs. for issue #515
|
Closing this since the issue is out of our hands. All we can do is look to host our own service and that is captured in #459. |
No description provided.
The text was updated successfully, but these errors were encountered: