Skip to content

Wire batch buffer limit (1GB) into durable emitter - #2538

Open
DylanTinianov wants to merge 1 commit into
mainfrom
CRE-7317-durable-emitter-batch-bytes-limit
Open

DylanTinianov wants to merge 1 commit into
mainfrom
CRE-7317-durable-emitter-batch-bytes-limit

Conversation

@DylanTinianov

@DylanTinianov DylanTinianov commented Nov 6, 2026 •

Copy link
Copy Markdown
Contributor

Description

Wires the chip ingress batch client's WithMaxBufferedBytes opt into the durable emitter with a 1GB default.

@DylanTinianov DylanTinianov self-assigned this Nov 6, 2026
@github-actions

github-actions Bot commented Nov 6, 2026

Copy link
Copy Markdown
Contributor

✅ API Diff Results - github.com/smartcontractkit/chainlink-common

✅ Compatible Changes (1)

pkg/durableemitter.SetupConfig (1)
  • MaxBufferedBytes — ➕ Added

📄 View full apidiff report

@DylanTinianov
DylanTinianov marked this pull request as ready for review November 6, 2026 16:06
@DylanTinianov
DylanTinianov requested a review from a team as a code owner November 6, 2026 16:06
@DylanTinianov DylanTinianov changed the title Wire batch buffered-bytes limit (1GB) into durable emitter Wire batch buffer limit (1GB) into durable emitter Nov 6, 2026
chipingressbatch.WithBatchInterval(defaultDuration(cfg.BatchInterval, 50*time.Millisecond)),
chipingressbatch.WithMaxConcurrentSends(defaultInt(cfg.MaxConcurrentSends, 4)),
chipingressbatch.WithMessageBuffer(defaultInt(cfg.MessageBufferSize, 10_000)),
chipingressbatch.WithMaxBufferedBytes(defaultInt64(cfg.MaxBufferedBytes, 1<<30)),

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Either add a comment here explaining this corresponds to a gigabyte or convert it to a var that makes it clear it is

eg 1024 * 1024 * 1024

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants