Skip to content

Commit 229b190

Browse files
committed
4.7.21 release notes
1 parent b520752 commit 229b190

2 files changed

Lines changed: 16 additions & 0 deletions

File tree

release-notes/v4-tucker/4.7.21.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
---
2+
title: 4.7.21
3+
---
4+
5+
# 4.7.21
6+
7+
3/6/2026
8+
9+
- Don't send a `Content-Length: 0` header for responses to HEAD requests.
10+
- Fix the coalescing time function to properly stream instead of buffering.
11+
- Improve support for prioritizing certifications by usage and allow for alternate name/primary key assignment.
12+
- Add support for configuring the maximum payload of replication connections.

versioned_docs/version-4.7/deployments/configuration.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -598,6 +598,10 @@ When true, Harper will attempt to fail-over to subscribing to a different node i
598598

599599
This defines the shard id of this instance and is used in conjunction with the [Table Resource functions](../developers/replication/sharding#custom-sharding) `setResidency` & `setResidencyById` to programmatically route traffic to the proper shard.
600600

601+
`maxPayload` - _Type_: integer; _Default_: 100000000 (100MB)
602+
603+
This sets the maximum payload size for replication messages.
604+
601605
---
602606

603607
### `clustering` using NATS

0 commit comments

Comments
 (0)