[KUDU-1895] Document the effects of non-renewable authn tokens

• Type: Task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.3.0
• Component/s: documentation
• Assignee: Unassigned
• Reporter: Alexey Serbin
• Created: 23/Feb/17 03:31
• Updated: 01/Mar/17 17:45

Description

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.