failed mapping AST context canceled

[RobbanHoglund]

Describe the bug
After upgrade to Loki 3.2.0 it is repeatedly logging this for some queries:
ts=2024-10-04T01:09:28.649297614Z caller=spanlogger.go:111 middleware=QueryShard.astMapperware org_id=fake traceID=35d59f6204919421 user=fake caller=log.go:168 level=warn msg="failed mapping AST" err="context canceled" query="{application="myapp",level=~"INFO|WARN|ERROR"} "

To Reproduce
Steps to reproduce the behavior:

1. Started Loki 3.2.0
2. From Grafana explore do {application="myapp",level=~"INFO|WARN|ERROR|TRACE"}

Expected behavior
If this is an actual problem in Loki 3.2.0 it would be good to get more information about what is the root cause.

Environment:

• Infrastructure: bare-metal
• Deployment tool: bash scripts

Screenshots, Promtail config, or terminal output
If applicable, add any output to help explain your problem.

[jammiemil]

Also seeing this in a cluster running 3.2.0, however its only happening on one of our Read pods (Running SSD via Helm), the same pod is reporting High query latency (upto 50s), and reporting a fair amount of context cancelled in the logs, All the other read pods are behaving just fine and returning query in sub-seconds