[ACCUMULO-2334] Lacking fallback when ACCUMULO_LOG_HOST isn't set

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.5.0
• Fix Version/s: 1.5.1, 1.6.0
• Component/s: tserver
• Assignee: Josh Elser
• Reporter: Josh Elser
• Created: 06/Feb/14 22:34
• Updated: 27/Aug/14 17:28
• Resolved: 11/Feb/14 20:25

Description

For log-forwarding, if ACCUMULO_LOG_HOST is not set, the code falls back to using the hostname for localhost.

We already have an address for the monitor in ZK; we should use that instead when populated.

Issue Links

• breaks: ACCUMULO-2373 Daemons should be able to log if log4j.properties specifies sufficient logging
• breaks: ACCUMULO-2425 ConcurrentModificationException in master at startup
• relates to: ACCUMULO-3086 start-all.sh and stop-all.sh ignore the monitor configuration file
• supercedes: ACCUMULO-1736 Monitor log forwarding breaks if monitors file starts with a NL
• links to: ReviewBoard