Return-Path: X-Original-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 46C6DE868 for ; Tue, 26 Feb 2013 23:29:41 +0000 (UTC) Received: (qmail 32896 invoked by uid 500); 26 Feb 2013 23:29:36 -0000 Delivered-To: apmail-hadoop-hdfs-user-archive@hadoop.apache.org Received: (qmail 32623 invoked by uid 500); 26 Feb 2013 23:29:36 -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 32611 invoked by uid 99); 26 Feb 2013 23:29:36 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Feb 2013 23:29:36 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of hadoop.ca@gmail.com designates 209.85.216.45 as permitted sender) Received: from [209.85.216.45] (HELO mail-qa0-f45.google.com) (209.85.216.45) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Feb 2013 23:29:29 +0000 Received: by mail-qa0-f45.google.com with SMTP id g10so2905914qah.4 for ; Tue, 26 Feb 2013 15:29:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=SoO/M7F5B73SpDtTZ42cU84Hq2yz6btjeRdU9of6C1g=; b=CXU6Je+5zRS79aEKYjM3QViM0J+nez9J2ApCN1ZPwcocP6wuTE5xLu/5xe27nm6wBg OF7SqbOSkP48EbIA5SsDD8T42tKAK4ePm4IAOTVmsqPVBFPfPDq+jrgSz1LdB3iv/VP5 d/2DS/S7ShIScfXiTYfArMz4v1qgo7BcrGc1m1No9CMaEm0Si+l/ck/4V0dSG46U5pG7 POs04g+iiTbacAyOMvHQfpSrPSUEh4h/0REA6hQ+YynQG8umI1iDk7t/m+FLsRNOuCoy Fppv4zjJIbkxotnyyGgtVi7wDGmEMYV4jPpUUo2ZLEoxOs2ebhm9OzWlrRZgX7LjaxoC hR9g== MIME-Version: 1.0 X-Received: by 10.49.50.131 with SMTP id c3mr140090qeo.40.1361921348954; Tue, 26 Feb 2013 15:29:08 -0800 (PST) Received: by 10.49.49.234 with HTTP; Tue, 26 Feb 2013 15:29:08 -0800 (PST) Date: Tue, 26 Feb 2013 15:29:08 -0800 Message-ID: Subject: JobTracker security From: Serge Blazhievsky To: user@hadoop.apache.org Content-Type: multipart/alternative; boundary=047d7bd74e1a378a8004d6a90615 X-Virus-Checked: Checked by ClamAV on apache.org --047d7bd74e1a378a8004d6a90615 Content-Type: text/plain; charset=ISO-8859-1 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 --047d7bd74e1a378a8004d6a90615 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi all,

Is there a way to restrict job monitoring and ma= nagement only to jobs started by each individual user?

The basic scenario is:

1. Star= t a job under user1

2. Login as user2=A0

3. hadoop job -list to retrieve job id<= /div>

4. hadoop job -kill job_id

5. Job gets terminated....= =A0

Is there something that needs to be enabled to= prevent that from happening?

Thanks

Serge

--047d7bd74e1a378a8004d6a90615--