accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-3773) ClientConfiguration create repeatedly in server processes
Date Tue, 09 Jun 2015 19:13:00 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-3773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14579422#comment-14579422
] 

Christopher Tubbs commented on ACCUMULO-3773:
---------------------------------------------

Dropping 1.6.3 from the fixVersion on this. I'm not sure this affects 1.6 at all. The log
message described above doesn't exist in 1.6, and the only places I saw it constructed repeatedly
that might cause this was in tests and mapreduce, where it would kind of make sense.

> ClientConfiguration create repeatedly in server processes
> ---------------------------------------------------------
>
>                 Key: ACCUMULO-3773
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3773
>             Project: Accumulo
>          Issue Type: Bug
>          Components: gc, master, tserver
>            Reporter: Josh Elser
>            Priority: Critical
>             Fix For: 1.6.3, 1.7.1, 1.8.0
>
>
> In looking at ACCUMULO-3772, I'm seeing loads of the following:
> {noformat}
> 2015-05-04 08:30:15,703 [client.ClientConfiguration] WARN : Client configuration constructed
with a Configuration that did not have list delimiter disabled or overridden, multi-valued
config properties may be unavailable
> 2015-05-04 08:30:15,764 [client.ClientConfiguration] WARN : Client configuration constructed
with a Configuration that did not have list delimiter disabled or overridden, multi-valued
config properties may be unavailable
> 2015-05-04 08:30:16,136 [client.ClientConfiguration] WARN : Client configuration constructed
with a Configuration that did not have list delimiter disabled or overridden, multi-valued
config properties may be unavailable
> 2015-05-04 08:30:16,185 [client.ClientConfiguration] WARN : Client configuration constructed
with a Configuration that did not have list delimiter disabled or overridden, multi-valued
config properties may be unavailable
> 2015-05-04 08:30:16,272 [client.ClientConfiguration] WARN : Client configuration constructed
with a Configuration that did not have list delimiter disabled or overridden, multi-valued
config properties may be unavailable
> 2015-05-04 08:30:17,621 [client.ClientConfiguration] WARN : Client configuration constructed
with a Configuration that did not have list delimiter disabled or overridden, multi-valued
config properties may be unavailable
> 2015-05-04 08:30:17,706 [client.ClientConfiguration] WARN : Client configuration constructed
with a Configuration that did not have list delimiter disabled or overridden, multi-valued
config properties may be unavailable
> 2015-05-04 08:30:17,717 [client.ClientConfiguration] WARN : Client configuration constructed
with a Configuration that did not have list delimiter disabled or overridden, multi-valued
config properties may be unavailable
> 2015-05-04 08:30:17,842 [client.ClientConfiguration] WARN : Client configuration constructed
with a Configuration that did not have list delimiter disabled or overridden, multi-valued
config properties may be unavailable
> 2015-05-04 08:30:17,857 [client.ClientConfiguration] WARN : Client configuration constructed
with a Configuration that did not have list delimiter disabled or overridden, multi-valued
config properties may be unavailable
> 2015-05-04 08:30:17,885 [client.ClientConfiguration] WARN : Client configuration constructed
with a Configuration that did not have list delimiter disabled or overridden, multi-valued
config properties may be unavailable
> 2015-05-04 08:30:18,071 [client.ClientConfiguration] WARN : Client configuration constructed
with a Configuration that did not have list delimiter disabled or overridden, multi-valued
config properties may be unavailable
> {noformat}
> The log message spam is annoying, but I think it's also indicative of a large problem
where we are repeatedly re-creating the same ClientConfiguration object over and over again.
This is wasteful and unnecessary as the contents of the ClientConfiguration can be static
for the lifetime of the server process.
> Need to identify if ClientConfiguration objects are being repeatedly created in the server
processes (potentially via AccumuloServerContext) and fix the calling code to avoid the annoying
log message over and over.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message