WARN tokio-runtime-worker db::pin: Pinned block cache limit reached.
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- rust
- Domain
- backend, distributed-systems
Research direction
Start by reviewing the attached AzeroLogs.txt together with the reported r-13.4 mainnet validator configuration and the repeated db::pin warnings. Determine whether the pinned block cache eviction is expected and whether it affects node health or the reported 3/18 rate; document the cause and a verified resolution.
Written by the indexing model from the issue text.
Description
Did you read the documentation and guides?
- I have inspected the documentation.
Is there an existing issue?
- I have searched the existing issues.
Description of the problem
When i check logs, i receive below errors/warnings. And when i check my node stats on azero.live, i see 3/18 rate.
2024-11-18 16:52:45.158 INFO tokio-runtime-worker substrate: ✨ Imported #95174217 (0xadf2…32bc)
2024-11-18 16:52:46.174 WARN tokio-runtime-worker db::pin: Pinned block cache limit reached. Evicting value. hash = 0x9673…c3e1
2024-11-18 16:52:46.174 INFO tokio-runtime-worker substrate: ✨ Imported #95174218 (0x6c4b…2d27)
2024-11-18 16:52:46.851 INFO tokio-runtime-worker substrate: 💤 Idle (9 peers), best: #95174218 (0x6c4b…2d27), finalized #95174217 (0xadf2…32bc), ⬇ 142.6kiB/s ⬆ 136.3kiB/s
2024-11-18 16:52:47.089 WARN tokio-runtime-worker db::pin: Pinned block cache limit reached. Evicting value. hash = 0xd6b4…9168
2024-11-18 16:52:47.090 INFO tokio-runtime-worker substrate: ✨ Imported #95174219 (0xfe66…2081)
2024-11-18 16:52:48.153 WARN tokio-runtime-worker db::pin: Pinned block cache limit reached. Evicting value. hash = 0x3c5d…d073
2024-11-18 16:52:48.154 INFO tokio-runtime-worker substrate: ✨ Imported #95174220 (0x754e…bdbe)
2024-11-18 16:52:49.115 WARN tokio-runtime-worker db::pin: Pinned block cache limit reached. Evicting value. hash = 0x7942…b05e
2024-11-18 16:52:49.115 INFO tokio-runtime-worker substrate: ✨ Imported #95174221 (0x7c9e…91f6)
2024-11-18 16:52:50.178 WARN tokio-runtime-worker db::pin: Pinned block cache limit reached. Evicting value. hash = 0x6d0e…8b8c
2024-11-18 16:52:50.179 INFO tokio-runtime-worker substrate: ✨ Imported #95174222 (0x6d80…c1b8)
2024-11-18 16:52:51.136 WARN tokio-runtime-worker db::pin: Pinned block cache limit reached. Evicting value. hash = 0xaf3c…bf59
2024-11-18 16:52:51.136 INFO tokio-runtime-worker substrate: ✨ Imported #95174223 (0xb5de…0e96)
Information on your setup.
- mainnet
- r-13.4
- aleph-node-runner
- validator node
- --mainnet
- Ubuntu 22.04.5 LTS
- 8 vCPU Cores / 24 GB RAM / 1.2 TB SSD / 600 Mbit connection
AzeroLogs.txt
Steps to reproduce
No response
Did you attach relevant logs?
- I have attached logs (if relevant).
- Dominant language
- No language data
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Cardinal-Cryptography/aleph-node-issues
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Cardinal-Cryptography/aleph-node-issues#16 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Cardinal-Cryptography/aleph-node-issues#14 · 5 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Cardinal-Cryptography/aleph-node-issues#13 · 4 comments ·
All issues in Cardinal-Cryptography/aleph-node-issues
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
PedestrianDynamics/pyFDS-Evac#343 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
containers/podman-py#662 ·
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
supabase/agent-skills#613 ·