Return-Path: X-Original-To: apmail-hadoop-common-user-archive@www.apache.org Delivered-To: apmail-hadoop-common-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 66A1CE8F9 for ; Wed, 27 Feb 2013 00:39:35 +0000 (UTC) Received: (qmail 48727 invoked by uid 500); 27 Feb 2013 00:39:30 -0000 Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org Received: (qmail 48626 invoked by uid 500); 27 Feb 2013 00:39:30 -0000 Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hadoop.apache.org Delivered-To: mailing list user@hadoop.apache.org Received: (qmail 48616 invoked by uid 99); 27 Feb 2013 00:39:30 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Feb 2013 00:39:30 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [74.125.82.174] (HELO mail-we0-f174.google.com) (74.125.82.174) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Feb 2013 00:39:23 +0000 Received: by mail-we0-f174.google.com with SMTP id r6so4024992wey.19 for ; Tue, 26 Feb 2013 16:39:03 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:content-type:x-gm-message-state; bh=hf+1+X0NnW1L+8dHjjo9Rb9QpMzfQagNAPzwHlF+eQc=; b=as4tzVO92HeAZyeAdm2J3tKVLwKmlEgdnA8xU8GtkfkAXRXsymarX4dVkaIQgAFhRv 1AODDdga3775EZRopRJ68u5qXSMcso3Pjv7UG5jC65YiKMJI3wSUFUOTQk8QGrHQAP+n Hgufo7f3eegPFwVvox2YLFzHYmZ9bTkZ2s7Q6zpHJK+Ug9tpR4bueUE+0VLYF2pbeRqK J7xnsAfxNujYjwaeczVq8vW3OrWHcv41wHqealufZBSakPbYytCMaKLlq5/JgJK0Xxma xb6V68uQVZ4esmWB9ylzOosID0fBjjNoKQmDJfRPyriJTCSUPQoclbVfxhUMv9vFf2zR y7UQ== X-Received: by 10.194.7.196 with SMTP id l4mr390627wja.28.1361925543491; Tue, 26 Feb 2013 16:39:03 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.176.71 with HTTP; Tue, 26 Feb 2013 16:38:43 -0800 (PST) In-Reply-To: References: From: Jean-Marc Spaggiari Date: Tue, 26 Feb 2013 19:38:43 -0500 Message-ID: Subject: Re: JobTracker security To: user@hadoop.apache.org Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQkCkHAlGHv6KdjG/TEWJs2jufoVG58YJrpe0LtzBJ84WjYVAgZikxIrZ8zPn1msxaEO/Bpa X-Virus-Checked: Checked by ClamAV on apache.org Maybe restrict access to the hadoop file(s) to the user1? 2013/2/26 Serge Blazhievsky : > I am trying to not to use kerberos... > > Is there other option? > > Thanks > Serge > > > On Tue, Feb 26, 2013 at 3:31 PM, Patai Sangbutsarakum > wrote: >> >> Kerberos >> >> From: Serge Blazhievsky >> Reply-To: >> Date: Tue, 26 Feb 2013 15:29:08 -0800 >> To: >> Subject: JobTracker security >> >> Hi all, >> >> Is there a way to restrict job monitoring and management only to jobs >> started by each individual user? >> >> >> The basic scenario is: >> >> 1. Start a job under user1 >> 2. Login as user2 >> 3. hadoop job -list to retrieve job id >> 4. hadoop job -kill job_id >> 5. Job gets terminated.... >> >> Is there something that needs to be enabled to prevent that from >> happening? >> >> Thanks >> Serge > >