Mailing-List: contact issues-help@spark.apache.org; run by ezmlm
Precedence: bulk
Date: Mon, 28 Nov 2016 20:36:59 +0000 (UTC)
From: "Alex Bozarth (JIRA)" <jira@apache.org>
To: issues@spark.apache.org
Message-ID: <JIRA.13022678.1479860389000.381626.1480365419661@Atlassian.JIRA>
In-Reply-To: <JIRA.13022678.1479860389000@Atlassian.JIRA>
References: <JIRA.13022678.1479860389000@Atlassian.JIRA> <JIRA.13022678.1479860389379@arcas>
Subject: [jira] [Commented] (SPARK-18551) Add functionality to delete event
 logs from the History Server UI
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 28 Nov 2016 20:37:01 -0000


    [ https://issues.apache.org/jira/browse/SPARK-18551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15703052#comment-15703052 ] 

Alex Bozarth commented on SPARK-18551:
--------------------------------------

Thanks for the feedback [~vanzin], I've paused work on my PR while we discuss what you've brought up. 

For your first point, my thinking was that the person who started the SHS and enabled the deletion config would be the liable user. This would/should be clearly documented. This means that in would be on the "sysadmin" who started the SHS to secure the SHS since anyone with access could delete apps. 
I'm not quite sure what you mean about the UI's auth code though, are you referring to the security manager? Since the security manager was already instantiated in the history server I assumed it was fair to use, though again it only looks at the startup user.

The second point is one I hadn't thought of though, as long as it's documented as such I don't see the issue with the logs showing the SHS user for every deletion. I agree that trying to get the web user's username to the logs is lots of unnecessary work.

The use case that raised this issue is when a user is given a SHS by their admin to access their app ui's and it only shows their apps and only they (and the admin) can access it. The user here has no access to the log folder without going through their admin.

As for [~stevel@apache.org]'s GET comment, I plan to fix that, it was a leftover from [~srowen]'s update to the kill stage code that I kept because (at the time) I didn't understand its purpose (Its for YARN, which doesn't apply here). 

If you still think this is an unsalvageable idea I will close this, I respect your opinion [~vanzin]

> Add functionality to delete event logs from the History Server UI
> -----------------------------------------------------------------
>
>                 Key: SPARK-18551
>                 URL: https://issues.apache.org/jira/browse/SPARK-18551
>             Project: Spark
>          Issue Type: New Feature
>          Components: Spark Core, Web UI
>            Reporter: Alex Bozarth
>
> Sometimes a Spark user will only have access to a History Server to interact with their (past) applications. But without access to the server they can only delete applications through use of the FS Cleaner feature, which itself can only clean logs older than a set date. 
> I propose adding the ability to delete specific applications via the History Server UI with the default setting to off.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org