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

Ashish Paliwal commented on FLUME-2636:
---------------------------------------

https://issues.apache.org/jira/browse/FLUME-1817
This one is related. There is one more related JIRA, unfortunately couldn't 
find it. I remember having read. It had discussion related to monitoring params 
passed as -D options as being a quick fix.

Sorry my memory fails me, getting old. Please keep working on the fix. Shall do 
one iteration on JIRA's and shall link it when found.

[~hshreedharan] Do you recall this discussion? I believe you had put a comment 
about the same

> Agent wide context for configuring shareable properties
> -------------------------------------------------------
>
>                 Key: FLUME-2636
>                 URL: https://issues.apache.org/jira/browse/FLUME-2636
>             Project: Flume
>          Issue Type: Improvement
>            Reporter: Johny Rufus
>            Assignee: Johny Rufus
>             Fix For: v1.6.0
>
>
> In secure mode, HDFSSink, HbaseSink, DataSetSink, (ThriftSource, ThriftSink  
> - in the future) all need to make use of the same kerberos principal and 
> keytab, and we have to manually  configure kerberos principal/keytab for each 
> of these components, with the same values.
> If we have an agent wide context, that is accessible from every component, 
> then we just need to configure the properties once, that can be accessed by 
> all secure components



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

Reply via email to