[
https://issues.apache.org/jira/browse/OOZIE-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16789290#comment-16789290
]
Andras Salamon commented on OOZIE-2338:
---------------------------------------
Thanks for the explanation [~nobigo]. I now see the reason for omitting some of
the previous patch. It seems to me some of the e-mail settings (e.g.
{{oozie.email.blacklist.*}} were not added to {{oozie-default.xml}}. Similarly
the patch also refers to
{{oozie.service.HCatAccessorService.hcat.configuration}}. Could you please
check those properties?
> Invalid configuration defined reported for some valid configs
> -------------------------------------------------------------
>
> Key: OOZIE-2338
> URL: https://issues.apache.org/jira/browse/OOZIE-2338
> Project: Oozie
> Issue Type: Bug
> Components: core
> Affects Versions: 4.2.0
> Reporter: Robert Kanter
> Assignee: duan xiong
> Priority: Major
> Attachments: OOZIE-2338.001.patch, OOZIE-2338.002.patch,
> oozie-2338-003.patch, oozie-2338-004.patch
>
>
> OOZIE-1890 moved all default config values from the code and oozie-site into
> oozie-default; it also added a WARN message on startup when a config is found
> in oozie-site that's not defined in oozie-default.
> However, this can produce some false positives. In particular, we observed
> these:
> {noformat}
> 2015-08-18 01:16:32,365 WARN org.apache.oozie.service.ConfigurationService:
> SERVER[<redacted>] Invalid configuration defined, [oozie.email.smtp.auth]
> 2015-08-18 01:16:32,365 WARN org.apache.oozie.service.ConfigurationService:
> SERVER[<redacted>] Invalid configuration defined, [oozie.email.smtp.host]
> 2015-08-18 01:16:32,365 WARN org.apache.oozie.service.ConfigurationService:
> SERVER[<redacted>] Invalid configuration defined,
> [oozie.service.HCatAccessorService.hcat.configuration]
> 2015-08-18 01:16:32,365 WARN org.apache.oozie.service.ConfigurationService:
> SERVER[<redacted>] Invalid configuration defined, [oozie.email.from.address]
> 2015-08-18 01:16:32,366 WARN org.apache.oozie.service.ConfigurationService:
> SERVER[<redacted>] Invalid configuration defined,
> [oozie.service.ProxyUserService.proxyuser.hue.hosts]
> 2015-08-18 01:16:32,366 WARN org.apache.oozie.service.ConfigurationService:
> SERVER[<redacted>] Invalid configuration defined,
> [oozie.service.GroupsService.hadoop.security.group.mapping]
> 2015-08-18 01:16:32,366 WARN org.apache.oozie.service.ConfigurationService:
> SERVER[<redacted>] Invalid configuration defined, [oozie.email.smtp.port]
> 2015-08-18 01:16:32,366 WARN org.apache.oozie.service.ConfigurationService:
> SERVER[<redacted>] Invalid configuration defined,
> [oozie.service.ProxyUserService.proxyuser.hue.groups]
> {noformat}
> While harmful, these messages may be concerning or confusing for users.
> Some of these are simply missing from oozie-default (because they have no
> default value?), while others such as the ProxyUserService configs, will
> require special handling because the property name can vary.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
