Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 9D196200C1B for ; Tue, 14 Feb 2017 19:12:45 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 9BB30160B5F; Tue, 14 Feb 2017 18:12:45 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id E76E4160B45 for ; Tue, 14 Feb 2017 19:12:44 +0100 (CET) Received: (qmail 51727 invoked by uid 500); 14 Feb 2017 18:12:44 -0000 Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list issues@ambari.apache.org Received: (qmail 51717 invoked by uid 99); 14 Feb 2017 18:12:44 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 Feb 2017 18:12:44 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id B53F31A0092 for ; Tue, 14 Feb 2017 18:12:43 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-2.999] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id 2IKXn4eLWzIk for ; Tue, 14 Feb 2017 18:12:43 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id DF4535F659 for ; Tue, 14 Feb 2017 18:12:42 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 265D0E0059 for ; Tue, 14 Feb 2017 18:12:42 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id D60AF24119 for ; Tue, 14 Feb 2017 18:12:41 +0000 (UTC) Date: Tue, 14 Feb 2017 18:12:41 +0000 (UTC) From: "Bharat Viswanadham (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMBARI-19996) Perform kinit on Kafka Start MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 14 Feb 2017 18:12:45 -0000 [ https://issues.apache.org/jira/browse/AMBARI-19996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated AMBARI-19996: ---------------------------------------- Status: Patch Available (was: Open) > Perform kinit on Kafka Start > ---------------------------- > > Key: AMBARI-19996 > URL: https://issues.apache.org/jira/browse/AMBARI-19996 > Project: Ambari > Issue Type: Task > Components: ambari-server > Reporter: Bharat Viswanadham > Assignee: Bharat Viswanadham > Attachments: AMBARI-19996.PATCH > > > Perform Kinit with kafka keytab on Kafka broker start. > As Kafka Client uses the cached kerberos ticket, so when kafka console commands like producer, consumer are run with kafka user and cluster is kerberoized, kinit should happen automatically -- This message was sent by Atlassian JIRA (v6.3.15#6346)