Alexey Serbin created KUDU-1895:
-----------------------------------

             Summary: Document effects of non-renewable authn tokens
                 Key: KUDU-1895
                 URL: https://issues.apache.org/jira/browse/KUDU-1895
             Project: Kudu
          Issue Type: Task
          Components: documentation
    Affects Versions: 1.3.0
            Reporter: Alexey Serbin


In Kudu an authn token, once issued, cannot be re-newed.  It might have some 
implications for end-users, since the token validity interval defines the 
longest possible lifetime of an external job/task (Spark, etc.) running against 
Kudu cluster if the job uses authn token for authentication.

Basically, it's necessary to document that the default authn token validity 
interval is set to 7 days (60 * 60 * 24 * 7 seconds) and if they expect to have 
longer jobs running with authn tokens, they should use 
{{--authn_token_validity_seconds}} command-line flag for Kudu master to set 
that validity interval accordingly.  Otherwise, a token can expire and the 
job/task would not be able to make any RPC calls to the Kudu cluster.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to