accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (ACCUMULO-3258) Warning about synconclose is way too spammy
Date Sat, 25 Oct 2014 02:33:33 GMT

     [ https://issues.apache.org/jira/browse/ACCUMULO-3258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Josh Elser resolved ACCUMULO-3258.
----------------------------------
    Resolution: Fixed

The warning will only be printed once per JVM per volume URI now. Also, refactored how {{Accumulo.init}}
works: split out initial log setup from {{Accumulo.init}} into its own method so we can make
sure that log4j is set up *before* we do anything else which might start using loggers (notably,
sync settings). This also makes sure that we actually get the warnings on the monitor instead
of to stdout.

> Warning about synconclose is way too spammy
> -------------------------------------------
>
>                 Key: ACCUMULO-3258
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3258
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: master, tserver
>    Affects Versions: 1.6.1
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>             Fix For: 1.6.2, 1.7.0
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> The location of the warning about {{dfs.datanode.synconclose}} not being set to true
is way too spammy. We only know to know about it once, not every time a volume is chosen.



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

Mime
View raw message