[
https://issues.apache.org/jira/browse/ACCUMULO-2372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14598683#comment-14598683
]
Christopher Tubbs commented on ACCUMULO-2372:
---------------------------------------------
As a compromise, I think we might be able to retain the existing *.err and
*.out files in conjunction with sending stuff to the POSIX logger. At least
then, we can enable system admins to monitor logs in a centralized way without
disrupting anybody else. And, we can discuss phasing out the *.err and *.out
files later.
I see all the launch scripts as basically ancillary to the core function of
Accumulo, though. Personally, I see our launch scripts as a basically separate
thing than Accumulo itself... something that would typically need to be
tailored for the downstream environment. We maintain them as a matter of
convenience for a reasonable out-of-the-box experience, but I don't really see
them as part of Accumulo itself.
systemd/journald seems to be the way things are moving forward in the Linux
community (which is not to say that's the only platform Accumulo supports, but
it is the largest), and these (along with utilities like jpackage) provide more
standardized means of launching services and handling log output for debugging
which are more integrated with other system services (though obviously, one
cannot discount Ambari, Docker, Mesos, etc.) As such, I think it's important to
keep these in mind in our scripts, and make sure to realize that the scripts
really aren't environment-agnostic, and maybe shouldn't be treated as permanent
fixtures in Accumulo's code, but as complimentary bits which primarily serve to
support one kind of environment (the out-of-box experience, launch from tarball
environment).
> Use POSIX logger for STDERR and STDOUT
> --------------------------------------
>
> Key: ACCUMULO-2372
> URL: https://issues.apache.org/jira/browse/ACCUMULO-2372
> Project: Accumulo
> Issue Type: Improvement
> Reporter: Christopher Tubbs
> Labels: newbie
> Fix For: 1.8.0
>
>
> Instead of piping STDOUT and STDERR to *.out and *.err files in our launch
> scripts, we should pipe to the POSIX cli logger (/usr/bin/logger) to log to
> the system logging facility at the desired log level.
> Incorporating the system logging facilities is useful for system
> administrators for troubleshooting and/or auditing. More integration with
> external logging facilities also means that we reduce our responsibility to
> maintain/manage the resulting logs to avoid problems (like filling up the
> local file system with logs), deferring that to utilities dedicated to that
> responsibility.
> The command-line options used for /usr/bin/logger should be enough to
> associate the logs with the particular process.
> (NOTE: Log4j can also be configured to use the system log facility, but that
> should be done through log4j configuration, with the appropriate log
> appender.)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
