, there really is
no
master
property to control the total aggregate size of all Kafka data
files
on
a
broker.
log.retention.size and log.file.size are great for managing data at
the
application level. In our case, application needs change
frequently,
and
performance itself is an ever evolving
understand this correctly, there really is
no
master
property to control the total aggregate size of all Kafka data
files
on
a
broker.
log.retention.size and log.file.size are great for managing data at
the
application level. In our case, application needs change
frequently
:
Thanks Jun. So if I understand this correctly, there really is no
master
property to control the total aggregate size of all Kafka data files
on
a
broker.
log.retention.size and log.file.size are great for managing data at
the
application level. In our case, application needs change
:31 AM, vinh v...@loggly.com wrote:
Thanks Jun. So if I understand this correctly, there really is no
master
property to control the total aggregate size of all Kafka data files on
a
broker.
log.retention.size and log.file.size are great for managing data at the
application level. In our case
...@loggly.com wrote:
Thanks Jun. So if I understand this correctly, there really is no
master
property to control the total aggregate size of all Kafka data files
on
a
broker.
log.retention.size and log.file.size are great for managing data at
the
application level. In our case
?
Thanks,
Jun
On Sun, May 4, 2014 at 4:31 AM, vinh v...@loggly.com wrote:
Thanks Jun. So if I understand this correctly, there really is no master
property to control the total aggregate size of all Kafka data files on a
broker.
log.retention.size and log.file.size are great for managing data
files on
a
broker.
log.retention.size and log.file.size are great for managing data at the
application level. In our case, application needs change frequently,
and
performance itself is an ever evolving feature. This means various
configs
are constantly changing, like topics, # of partitions
on a
broker.
log.retention.size and log.file.size are great for managing data at the
application level. In our case, application needs change frequently, and
performance itself is an ever evolving feature. This means various configs
are constantly changing, like topics, # of partitions, etc
, there really is no master
property to control the total aggregate size of all Kafka data files on a
broker.
log.retention.size and log.file.size are great for managing data at the
application level. In our case, application needs change frequently, and
performance itself is an ever evolving
Thanks Jun. So if I understand this correctly, there really is no master
property to control the total aggregate size of all Kafka data files on a
broker.
log.retention.size and log.file.size are great for managing data at the
application level. In our case, application needs change
log.retention.size controls the total size in a log dir (per
partition). log.file.size
controls the size of each log segment in the log dir.
Thanks,
Jun
On Thu, May 1, 2014 at 9:31 PM, vinh v...@loggly.com wrote:
In the 0.7 docs, the description for log.retention.size and log.file.size
Using Kafka 0.7.2, I have the following in server.properties:
log.retention.hours=48
log.retention.size=107374182400
log.file.size=536870912
My interpretation of this is:
a) a single log segment file over 48hrs old will be deleted
b) the total combined size of *all* logs is 100GB
c) a single log
In the 0.7 docs, the description for log.retention.size and log.file.size sound
very much the same. In particular, that they apply to a single log file (or
log segment file).
http://kafka.apache.org/07/configuration.html
I'm beginning to think there is no setting to control the max aggregate
13 matches
Mail list logo
