[jira] [Commented] (YARN-3180) container-executor gets SEGV for default banned user

2015-02-11 Thread Olaf Flebbe (JIRA)

[ 
https://issues.apache.org/jira/browse/YARN-3180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14317142#comment-14317142
 ] 

Olaf Flebbe commented on YARN-3180:
---

Seems like it. The fix to the logic is the same. The test is different. I do 
test the exact environment, the other test does test much more than simply the 
check_user() call.

The patch does not apply on git trunk.

please apply either .

 container-executor gets SEGV for default banned user
 

 Key: YARN-3180
 URL: https://issues.apache.org/jira/browse/YARN-3180
 Project: Hadoop YARN
  Issue Type: Bug
Affects Versions: 2.4.1, 2.6.1
Reporter: Olaf Flebbe
 Attachments: 
 0001-YARN-3180-container-executor-gets-SEGV-for-default-b.patch


 container-executor dumps core if container-executor.cfg 
 * Does not contain a banned.users statement, getting the default in effect
 * The banned user id is above min.user.id
 * The user is contained in the default banned.user
 and yes this did happened to me.
 Patch and test appended (relativ to git trunk)
  



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


[jira] [Commented] (YARN-3180) container-executor gets SEGV for default banned user

2015-02-11 Thread Jason Lowe (JIRA)

[ 
https://issues.apache.org/jira/browse/YARN-3180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14317111#comment-14317111
 ] 

Jason Lowe commented on YARN-3180:
--

Is this a dup of YARN-2847?

 container-executor gets SEGV for default banned user
 

 Key: YARN-3180
 URL: https://issues.apache.org/jira/browse/YARN-3180
 Project: Hadoop YARN
  Issue Type: Bug
Affects Versions: 2.4.1, 2.6.1
Reporter: Olaf Flebbe
 Attachments: 
 0001-YARN-3180-container-executor-gets-SEGV-for-default-b.patch


 container-executor dumps core if container-executor.cfg 
 * Does not contain a banned.users statement, getting the default in effect
 * The banned user id is above min.user.id
 * The user is contained in the default banned.user
 and yes this did happened to me.
 Patch and test appended (relativ to git trunk)
  



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