Cache receiving stalled
See original GitHub issueThe same log line repeating indefinitely for 40+ minutes:
Received 1653791515 of 1662180123 (99.5%)
![image](https://user-images.githubusercontent.com/7342379/191427716-7e5aaea9-acba-4c4d-84f0-7446aa56c8e8.png)
- name: Cache dataset
uses: actions/cache@v3
with:
path: tests/S1A_Stack_CPGF_T173.tar.gz
key: S1A_Stack_CPGF_T173.tar.gz
restore-keys: S1A_Stack_CPGF_T173
This is the link to the job: https://github.com/mobigroup/gmtsar/actions/runs/3095306955/jobs/5009583727
Issue Analytics
- State:
- Created a year ago
- Comments:7
Top Results From Across the Web
Does processor stall during cache coherence operation
It depends on the temporal occurences (race). As soon as as processor 1 updates a, the corresponding cache line in processor 2 is...
Read more >Unable to cancel stalled cache processing job
To stop any cache job is in progress, stop the caching gp service. To fix the cache status, run "ManageMapServerCacheStatus" tool with update ......
Read more >LVM Write Stalls When Cache Fills
I'm currently encountering a very perplexing issue with my media server. I have an LV set up with a few disks, and that...
Read more >Deploy stuck at "still downloading cache"
Hi there, I am doing my first deploy of an app, and I have gotten stuck at a very early phase in the...
Read more >Stalled cache updating - NGINX
Hi List, I'm getting this error in my logs every few minutes. ... 22203#0: *28358 stalled cache updating, error:0 while closing request, ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Could we remove the awaiting-customer-reponse label from the ticket as we can still confirm the issue is still not resolved.
I am seeing this as well, it is a major issue in my workflow, the primary reason why it is very unreliable.