Re: [DISCUSS] Change log.segment.bytes config type from int to long

Also here you can see guys have same idea https://forum.confluent.io/t/what-happens-if-i-increase-log-segment-bytes/5845 On Tue, 22 Apr 2025 at 15:41, Mikhail Fesenko wrote: > Currently we have big amount of topics and big data, and using high disk > storage, so rotate files too fast i

Re: [DISCUSS] Change log.segment.bytes config type from int to long

t; Jun > > On Thu, Feb 13, 2025 at 1:32 PM Mikhail Fesenko wrote: > > > Hi everyone, > > > > I’d like to propose a change the data type of log.segment.bytes from int > to > > long, allowing segment sizes beyond the current 2GB limit. > > > > Rationale: &

Re: [DISCUSS] Change log.segment.bytes config type from int to long

m int to long is a minor change, allowing or > encouraging users to create large segments requires stronger justification. > > thanks, > Chia-Ping > > > Mikhail Fesenko 於 2025年2月21日 週五 下午10:31寫道： > > > Guys, any thoughts on that? Please let me know! > > > >

Re: [DISCUSS] Change log.segment.bytes config type from int to long

Guys, any thoughts on that? Please let me know! On Thu, 13 Feb 2025 at 22:31, Mikhail Fesenko wrote: > Hi everyone, > > I’d like to propose a change the data type of log.segment.bytes from int > to long, allowing segment sizes beyond the current 2GB limit. > > Rationale:

[DISCUSSION] replication when replica.fetch.response.max.bytes bigger than fetch.max.bytes

HI everyone, I'm trying to understand the relationship between fetch.max.bytes and replica.fetch.response.max.bytes in Apache Kafka. According to the KIP-541 documentation , fetch.m

[DISCUSS] Change log.segment.bytes config type from int to long

capabilities. Would love to hear your thoughts ! Best, Mikhail Fesenko

KIP Proposal: Increase Log Segment Size Limit

capabilities. Would love to hear your thoughts before drafting a formal KIP. Best, Mikhail Fesenko