# Weaviate shard in readonly during quantization 8bit

**URL:** https://forum.weaviate.io/t/weaviate-shard-in-readonly-during-quantization-8bit/22223
**Category:** Support
**Tags:** bug, technical
**Created:** [January 20, 2026, 4:38pm UTC](https://forum.weaviate.io/t/weaviate-shard-in-readonly-during-quantization-8bit/22223 "2026-01-20T16:38:53Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![Tibin](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/tibin/32/2445_2.png) [@Tibin](https://forum.weaviate.io/u/Tibin)
#### Post date: [January 20, 2026, 4:38pm UTC](https://forum.weaviate.io/t/weaviate-shard-in-readonly-during-quantization-8bit/22223/1 "2026-01-20T16:38:53Z")

</div>

### Description

Tried enabling quantization on an existing collection via the API. However, for one shard, indexing switches to read-only mode, and queries through the Python client fail intermittently.

I also restored an older backup and repeated the same experiment in a sandbox environment, but observed the same behavior. What could be causing this?

Server Setup Information

- Weaviate Server Version: 1.32
- Deployment Method: Helm, Kubernetes
- Multi Node: Yes, 3
- Client Language and Version: Python , enabled quantization through REST
- Multitenancy: No
- Replicas: 2

### Any additional Information

Time Event  
13:42:48 Shard initialized and loaded in ~7.5 seconds  
13:42:56 Shard marked as ready with 11,357,657 nodes  
13:47:48 Tombstone cleanup started - processing 437,804 tombstones  
13:47:48 - 13:48:04 Tombstone cleanup progressing (0 → 7M nodes processed)  
13:56:48 Compaction halted - shard entered READONLY status  
13:57:04-06 Multiple maintenance lock delays (\>100ms waits)  
14:09:12 Broadcast errors began - “read only” status  
14:33:30-31 Continued broadcast failures  
attaching the log file of weaivate-1 node where the shard is present [Please read](https://filebin.net/1heqenmi0gm1dm9j/weaviate-9.log)

 ![image](https://canada1.discourse-cdn.com/flex027/uploads/weaviate/original/2X/e/ee416c2263b1f48a9172959e9c499ac1b1f1f032.png)

---

<div class="post-metadata">

### Author: ![DudaNogueira](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/dudanogueira/32/7846_2.png) [@DudaNogueira](https://forum.weaviate.io/u/DudaNogueira)
#### Post date: [January 22, 2026, 1:20pm UTC](https://forum.weaviate.io/t/weaviate-shard-in-readonly-during-quantization-8bit/22223/2 "2026-01-22T13:20:59Z")

</div>

hi @Tibin !!

I see from logs you are using 1.32.0 ☹

The latest for this cut is 1.32.27 as I write: [Tags · weaviate/weaviate · GitHub](https://github.com/weaviate/weaviate/tags)

Can you reproduce on that version and/or, better yet, on latest [Release v1.35.3 - Bucket load limiter improvement, NaN average proplength Fix, multi2vec-voyageai module video modalilty support · weaviate/weaviate · GitHub](https://github.com/weaviate/weaviate/releases/tag/v1.35.3) ?

Thanks!