This is an automated email from the ASF dual-hosted git repository.
JingsongLi pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/paimon.git
The following commit(s) were added to refs/heads/master by this push:
new f2ae9f6800 [docs] Fix stale sink.writer-coordinator.cache-memory
default value (#8510)
f2ae9f6800 is described below
commit f2ae9f6800211a497b3834156d899a75c7079cbb
Author: Eunbin Son <[email protected]>
AuthorDate: Thu Jul 9 13:04:15 2026 +0900
[docs] Fix stale sink.writer-coordinator.cache-memory default value (#8510)
---
docs/docs/maintenance/write-performance.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/docs/maintenance/write-performance.md
b/docs/docs/maintenance/write-performance.md
index d1ca2a414d..fb8bfa4738 100644
--- a/docs/docs/maintenance/write-performance.md
+++ b/docs/docs/maintenance/write-performance.md
@@ -126,7 +126,7 @@ execution.checkpointing.timeout = 60 min
In the initialization of write, the writer of the bucket needs to read all
historical files. If there is a bottleneck
here (For example, writing a large number of partitions simultaneously), you
can use `sink.writer-coordinator.enabled`
to use a Flink coordinator to cache the read manifest data to accelerate
initialization. The cache memory for coordinator
-is `sink.writer-coordinator.cache-memory`, default is 1GB in Job Manager.
+is `sink.writer-coordinator.cache-memory`, default is 2GB in Job Manager.
The coordinator manifest cache normally holds entries with soft references, so
the JVM can reclaim them when the Job
Manager runs low on heap. On a heavily loaded Job Manager this can backfire:
the JVM reclaims cached manifests, writers
