[
https://issues.apache.org/jira/browse/AMBARI-12685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14680590#comment-14680590
]
Hudson commented on AMBARI-12685:
---------------------------------
ABORTED: Integrated in Ambari-branch-2.1 #352 (See
[https://builds.apache.org/job/Ambari-branch-2.1/352/])
AMBARI-12685 - EclipseLink stdout Log Statements Fill Up Disk Space
(jonathanhurley) (jhurley:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=d6405682d0ac49518a04dd140bde98143aa21283)
* ambari-server/conf/unix/log4j.properties
* ambari-server/conf/windows/log4j.properties
* ambari-server/src/main/conf/log4j.properties
*
ambari-server/src/main/java/org/apache/ambari/server/logging/EclipseLinkLogger.java
* ambari-server/src/main/resources/META-INF/persistence.xml
> EclipseLink stdout Log Statements Fill Up Disk Space
> ----------------------------------------------------
>
> Key: AMBARI-12685
> URL: https://issues.apache.org/jira/browse/AMBARI-12685
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.0.0
> Reporter: Jonathan Hurley
> Assignee: Jonathan Hurley
> Priority: Critical
> Fix For: 2.1.1
>
> Attachments: AMBARI-12685.patch
>
>
> EclipseLink's default logger logs to standard output. Since Ambari redirects
> stdout to a file, this means that all EclipseLink statements are captured in
> {{ambari-server.out}}.
> On some systems with latency problems, EclipseLink will log retry attempts:
> {code}
> ...
> [EL Info]: 2015-07-21 04:52:51.346--UnitOfWork(506587476)--Communication
> failure detected when attempting to perform read query outside of a
> transaction. Attempting to retry query. Error was: Exception
> [EclipseLink-4002] (Eclipse Persistence Services - 2.5.2.v20140319-9ad6abd):
> org.eclipse.persistence.exceptions.DatabaseException
> Internal Exception: org.postgresql.util.PSQLException: The connection attempt
> failed.
> Error Code: 0
> Query: ReadAllQuery(name="HostEntity.findByHostName"
> referenceClass=HostEntity sql="SELECT host_id, cpu_count, cpu_info,
> discovery_status, host_attributes, host_name, ipv4, ipv6,
> last_registration_time, os_arch, os_info, os_type, ph_cpu_count,
> public_host_name, rack_info, total_mem FROM hosts WHERE (host_name = ?)").
> [EL Severe]: 2015-07-21 04:52:51.347--ServerSession(1225946600)--Exception
> [EclipseLink-4002] (Eclipse Persistence Services - 2.5.2.v20140319-9ad6abd):
> org.eclipse.persistence.exceptions.DatabaseException
> Internal Exception: org.postgresql.util.PSQLException: Connection refused.
> Check that the hostname and port are correct and that the postmaster is
> accepting TCP/IP connections.
> Error Code: 0
> ...
> {code}
> Since this log is not rolling, it can fill up the disk.
> There is no log4j bridge for EclipseLink. This Jira will track the creation
> of an slf4j bridge that will log all SQL statements to a separate, rolling
> logger.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
