[
https://issues.apache.org/jira/browse/ZOOKEEPER-4507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17514149#comment-17514149
]
Christopher Tubbs commented on ZOOKEEPER-4507:
----------------------------------------------
This seems out of scope of ZooKeeper itself. Log collection and management is
typically a user responsibility. Even a small amount of complexity added to ZK
scripts to do this log rotation adds technical debt to the scripts that makes
it harder to fix other issues later. There are better tools for users for
managing their logs in their installed environment (logrotate, rsyslog,
journald, a simple systemd wrapper that archives logs on process launch
restart, etc.). Trivially, a user could just use a different log4j
configuration to use a ROLLINGFILE if that is what they need.
Launch scripts should be *very* simple, and I would argue against adding this
feature to them. This seems like scope creep to me. There are better tools to
empower users with to manage logs.
> Create ZOO_DAEMON_OUT file backup when restarting the server
> ------------------------------------------------------------
>
> Key: ZOOKEEPER-4507
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-4507
> Project: ZooKeeper
> Issue Type: Improvement
> Components: scripts
> Reporter: Mohammad Arshad
> Assignee: Mohammad Arshad
> Priority: Major
> Attachments: image-2022-03-29-20-33-57-181.png
>
>
> The ZooKeeper server deamon out file zookeeper-$USER-server-$HOSTNAME.out is
> overwritten on every server restart.
> Like the other log file we should create backup of this file also. Many times
> information logged into these file are useful in issue analysis. For example
> this contains the information about which transaction and which snapshot
> files were deleted. These are useful info, we should retain for some time.
> May be by default we can backup 5 .out files like below
> !image-2022-03-29-20-33-57-181.png!
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
