[jira] [Commented] (MAPREDUCE-7273) JHS: make sure that Kerberos relogin is performed when KDC becomes offline then online again
[
https://issues.apache.org/jira/browse/MAPREDUCE-7273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17085342#comment-17085342
]
Hudson commented on MAPREDUCE-7273:
---
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #18151 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/18151/])
MAPREDUCE-7273. Fixed Job History server token renewal.
(eyang: rev 053e39e1e458d6437481296ab528327f7241fc78)
* (edit)
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-hs/src/main/java/org/apache/hadoop/mapreduce/v2/hs/HistoryFileManager.java
> JHS: make sure that Kerberos relogin is performed when KDC becomes offline
> then online again
>
>
> Key: MAPREDUCE-7273
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-7273
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: jobhistoryserver
>Affects Versions: 2.10.0, 3.2.1, 3.1.3
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Major
> Fix For: 3.4.0
>
> Attachments: MAPREDUCE-7273-001.patch, MAPREDUCE-7273-002.patch
>
>
> In JHS, if the KDC goes offline, the IPC layer does try to relogin, but it's
> not always enough. You have to wait for 60 seconds for the next retry. In the
> meantime, if the KDC comes back, the following error might occur:
> {noformat}
> 2020-04-09 03:27:52,075 DEBUG ipc.Server (Server.java:processSaslToken(1952))
> - Have read input token of size 708 for processing by
> saslServer.evaluateResponse()
> 2020-04-09 03:27:52,077 DEBUG ipc.Server (Server.java:saslProcess(1829)) -
> javax.security.sasl.SaslException: GSS initiate failed [Caused by
> GSSException: Failure unspecified at GSS-API level (Mechanism level: Invalid
> argument (400) - Cannot find key of appropriate type to decrypt AP REP -
> AES128 CTS mode with HMAC SHA1-96)]
> at
> com.sun.security.sasl.gsskerb.GssKrb5Server.evaluateResponse(GssKrb5Server.java:199)
> ...
> {noformat}
> When this happens, JHS has to be restarted.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
[jira] [Commented] (MAPREDUCE-7273) JHS: make sure that Kerberos relogin is performed when KDC becomes offline then online again
[
https://issues.apache.org/jira/browse/MAPREDUCE-7273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17085325#comment-17085325
]
Eric Yang commented on MAPREDUCE-7273:
--
I just committed this. Thank you [~pbacsko].
> JHS: make sure that Kerberos relogin is performed when KDC becomes offline
> then online again
>
>
> Key: MAPREDUCE-7273
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-7273
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: jobhistoryserver
>Affects Versions: 2.10.0, 3.2.1, 3.1.3
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Major
> Fix For: 3.4.0
>
> Attachments: MAPREDUCE-7273-001.patch, MAPREDUCE-7273-002.patch
>
>
> In JHS, if the KDC goes offline, the IPC layer does try to relogin, but it's
> not always enough. You have to wait for 60 seconds for the next retry. In the
> meantime, if the KDC comes back, the following error might occur:
> {noformat}
> 2020-04-09 03:27:52,075 DEBUG ipc.Server (Server.java:processSaslToken(1952))
> - Have read input token of size 708 for processing by
> saslServer.evaluateResponse()
> 2020-04-09 03:27:52,077 DEBUG ipc.Server (Server.java:saslProcess(1829)) -
> javax.security.sasl.SaslException: GSS initiate failed [Caused by
> GSSException: Failure unspecified at GSS-API level (Mechanism level: Invalid
> argument (400) - Cannot find key of appropriate type to decrypt AP REP -
> AES128 CTS mode with HMAC SHA1-96)]
> at
> com.sun.security.sasl.gsskerb.GssKrb5Server.evaluateResponse(GssKrb5Server.java:199)
> ...
> {noformat}
> When this happens, JHS has to be restarted.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
[jira] [Updated] (MAPREDUCE-7273) JHS: make sure that Kerberos relogin is performed when KDC becomes offline then online again
[
https://issues.apache.org/jira/browse/MAPREDUCE-7273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Yang updated MAPREDUCE-7273:
-
Fix Version/s: 3.4.0
Target Version/s: 3.4.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> JHS: make sure that Kerberos relogin is performed when KDC becomes offline
> then online again
>
>
> Key: MAPREDUCE-7273
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-7273
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: jobhistoryserver
>Affects Versions: 2.10.0, 3.2.1, 3.1.3
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Major
> Fix For: 3.4.0
>
> Attachments: MAPREDUCE-7273-001.patch, MAPREDUCE-7273-002.patch
>
>
> In JHS, if the KDC goes offline, the IPC layer does try to relogin, but it's
> not always enough. You have to wait for 60 seconds for the next retry. In the
> meantime, if the KDC comes back, the following error might occur:
> {noformat}
> 2020-04-09 03:27:52,075 DEBUG ipc.Server (Server.java:processSaslToken(1952))
> - Have read input token of size 708 for processing by
> saslServer.evaluateResponse()
> 2020-04-09 03:27:52,077 DEBUG ipc.Server (Server.java:saslProcess(1829)) -
> javax.security.sasl.SaslException: GSS initiate failed [Caused by
> GSSException: Failure unspecified at GSS-API level (Mechanism level: Invalid
> argument (400) - Cannot find key of appropriate type to decrypt AP REP -
> AES128 CTS mode with HMAC SHA1-96)]
> at
> com.sun.security.sasl.gsskerb.GssKrb5Server.evaluateResponse(GssKrb5Server.java:199)
> ...
> {noformat}
> When this happens, JHS has to be restarted.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
[jira] [Commented] (MAPREDUCE-7273) JHS: make sure that Kerberos relogin is performed when KDC becomes offline then online again
[
https://issues.apache.org/jira/browse/MAPREDUCE-7273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17085070#comment-17085070
]
Eric Yang commented on MAPREDUCE-7273:
--
+1 for patch 2. Will commit, if no objections.
> JHS: make sure that Kerberos relogin is performed when KDC becomes offline
> then online again
>
>
> Key: MAPREDUCE-7273
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-7273
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: jobhistoryserver
>Affects Versions: 2.10.0, 3.2.1, 3.1.3
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Major
> Attachments: MAPREDUCE-7273-001.patch, MAPREDUCE-7273-002.patch
>
>
> In JHS, if the KDC goes offline, the IPC layer does try to relogin, but it's
> not always enough. You have to wait for 60 seconds for the next retry. In the
> meantime, if the KDC comes back, the following error might occur:
> {noformat}
> 2020-04-09 03:27:52,075 DEBUG ipc.Server (Server.java:processSaslToken(1952))
> - Have read input token of size 708 for processing by
> saslServer.evaluateResponse()
> 2020-04-09 03:27:52,077 DEBUG ipc.Server (Server.java:saslProcess(1829)) -
> javax.security.sasl.SaslException: GSS initiate failed [Caused by
> GSSException: Failure unspecified at GSS-API level (Mechanism level: Invalid
> argument (400) - Cannot find key of appropriate type to decrypt AP REP -
> AES128 CTS mode with HMAC SHA1-96)]
> at
> com.sun.security.sasl.gsskerb.GssKrb5Server.evaluateResponse(GssKrb5Server.java:199)
> ...
> {noformat}
> When this happens, JHS has to be restarted.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
[jira] [Commented] (MAPREDUCE-7274) Enable to set running task limit when mapreduce job is running
[ https://issues.apache.org/jira/browse/MAPREDUCE-7274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17084968#comment-17084968 ] Chengwei Wang commented on MAPREDUCE-7274: -- Hi [~jlowe] [~acmurthy] [~junping_du] Could you have time to review this patch? Thank you . > Enable to set running task limit when mapreduce job is running > -- > > Key: MAPREDUCE-7274 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-7274 > Project: Hadoop Map/Reduce > Issue Type: New Feature > Components: mr-am, mrv2 >Reporter: Chengwei Wang >Priority: Major > Attachments: MAPREDUCE-7274-branch-3.2.0.patch > > > MRv2 enabled users to control the number of map or reduce tasks running > simultaneously by configuration *_mapreduce.job.running.map.limit_* or > _*mapreduce.job.running.reduce.limit*._ But users can only set limit number > before submitting the job to rm. So, it's meaningful to enable users to set > the limit of running map or reduce tasks when job is running, which can help > users to restrict resource usage of job and give resources to high-priority > job. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
[jira] [Issue Comment Deleted] (MAPREDUCE-7274) Enable to set running task limit when mapreduce job is running
[ https://issues.apache.org/jira/browse/MAPREDUCE-7274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chengwei Wang updated MAPREDUCE-7274: - Comment: was deleted (was: I would upload a patch for hadoop 2.x or 3.2.0 if needed.) > Enable to set running task limit when mapreduce job is running > -- > > Key: MAPREDUCE-7274 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-7274 > Project: Hadoop Map/Reduce > Issue Type: New Feature > Components: mr-am, mrv2 >Reporter: Chengwei Wang >Priority: Major > Attachments: MAPREDUCE-7274-branch-3.2.0.patch > > > MRv2 enabled users to control the number of map or reduce tasks running > simultaneously by configuration *_mapreduce.job.running.map.limit_* or > _*mapreduce.job.running.reduce.limit*._ But users can only set limit number > before submitting the job to rm. So, it's meaningful to enable users to set > the limit of running map or reduce tasks when job is running, which can help > users to restrict resource usage of job and give resources to high-priority > job. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
[jira] [Comment Edited] (MAPREDUCE-7274) Enable to set running task limit when mapreduce job is running
[
https://issues.apache.org/jira/browse/MAPREDUCE-7274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17084662#comment-17084662
]
Chengwei Wang edited comment on MAPREDUCE-7274 at 4/16/20, 3:01 PM:
Upload patch for hadoop 3.2.0.
It enable us to set task running limit when job is running by mapred client
command:
{code:bash}
mapred job -set-running-task-limit JOB_ID TASK_TYPE LIMIT
e.g.
mapred job -set-running-task-limit job_1583809537551_21297 MAP 100
mapred job -set-running-task-limit job_1583809537551_21297 REDUCE 100
{code}
it send a rpc resquest to AM, and AM would update the max running limit of the
specified type task as specified limit count.
was (Author: smarthan):
Upload patch for hadoop 3.2.0.
It enable us to set task running limit when job is running by mapred client
command:
{code:bash}
mapred job -set-running-task-limit JOB_ID TASK_TYPE LIMIT
e.g.
mapred job -set-running-task-limit job_1583809537551_21297 MAP 100
mapred job -set-running-task-limit job_1583809537551_21297 REDUCE 100
{code}
it send a rpc resquest to AM, and AM would update the max running limit of the
specified type task as specified limit count.
> Enable to set running task limit when mapreduce job is running
> --
>
> Key: MAPREDUCE-7274
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-7274
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> Components: mr-am, mrv2
>Reporter: Chengwei Wang
>Priority: Major
> Attachments: MAPREDUCE-7274-branch-3.2.0.patch
>
>
> MRv2 enabled users to control the number of map or reduce tasks running
> simultaneously by configuration *_mapreduce.job.running.map.limit_* or
> _*mapreduce.job.running.reduce.limit*._ But users can only set limit number
> before submitting the job to rm. So, it's meaningful to enable users to set
> the limit of running map or reduce tasks when job is running, which can help
> users to restrict resource usage of job and give resources to high-priority
> job.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
[jira] [Updated] (MAPREDUCE-7274) Enable to set running task limit when mapreduce job is running
[ https://issues.apache.org/jira/browse/MAPREDUCE-7274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chengwei Wang updated MAPREDUCE-7274: - Description: MRv2 enabled users to control the number of map or reduce tasks running simultaneously by configuration *_mapreduce.job.running.map.limit_* or _*mapreduce.job.running.reduce.limit*._ But users can only set limit number before submitting the job to rm. So, it's meaningful to enable users to set the limit of running map or reduce tasks when job is running, which can help users to restrict resource usage of job and give resources to high-priority job. (was: MRv2 enabled users to control the number of map or reduce tasks running simultaneously by configuration _mapreduce.job.running.map.limit_ or _mapreduce.job.running.reduce.limit._ But users can only set limit number before submitting the job to rm. So, it's meaningful to enable users to set the limit of running map or reduce tasks when job is running, which can help users to restrict resource usage of job and give resources to high-priority job.) > Enable to set running task limit when mapreduce job is running > -- > > Key: MAPREDUCE-7274 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-7274 > Project: Hadoop Map/Reduce > Issue Type: New Feature > Components: mr-am, mrv2 >Reporter: Chengwei Wang >Priority: Major > Attachments: MAPREDUCE-7274-branch-3.2.0.patch > > > MRv2 enabled users to control the number of map or reduce tasks running > simultaneously by configuration *_mapreduce.job.running.map.limit_* or > _*mapreduce.job.running.reduce.limit*._ But users can only set limit number > before submitting the job to rm. So, it's meaningful to enable users to set > the limit of running map or reduce tasks when job is running, which can help > users to restrict resource usage of job and give resources to high-priority > job. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
[jira] [Commented] (MAPREDUCE-7273) JHS: make sure that Kerberos relogin is performed when KDC becomes offline then online again
[
https://issues.apache.org/jira/browse/MAPREDUCE-7273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17084785#comment-17084785
]
Hadoop QA commented on MAPREDUCE-7273:
--
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
28s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m
0s{color} | {color:red} The patch doesn't appear to include any new or modified
tests. Please justify why no new tests are needed for this patch. Also please
list what manual steps were performed to verify this patch. {color} |
|| || || || {color:brown} trunk Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 19m
3s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
29s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
21s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m
31s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} shadedclient {color} | {color:green}
14m 12s{color} | {color:green} branch has no errors when building and testing
our client artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m
45s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
23s{color} | {color:green} trunk passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
25s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
21s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
21s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
15s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m
24s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} shadedclient {color} | {color:green}
13m 17s{color} | {color:green} patch has no errors when building and testing
our client artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m
46s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
21s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 4m
2s{color} | {color:green} hadoop-mapreduce-client-hs in the patch passed.
{color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
33s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 57m 6s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=19.03.8 Server=19.03.8 Image:yetus/hadoop:e6455cc864d |
| JIRA Issue | MAPREDUCE-7273 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/13000125/MAPREDUCE-7273-002.patch
|
| Optional Tests | dupname asflicense compile javac javadoc mvninstall
mvnsite unit shadedclient findbugs checkstyle |
| uname | Linux 1523a2606d8f 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6
11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | /testptch/patchprocess/precommit/personality/provided.sh |
| git revision | trunk / cc5c1da |
| maven | version: Apache Maven 3.3.9 |
| Default Java | 1.8.0_242 |
| findbugs | v3.1.0-RC1 |
| Test Results |
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/7766/testReport/ |
| Max. process+thread count | 444 (vs. ulimit of 5500) |
| modules | C:
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-hs U:
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-hs |
| Console output |
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/7766/console |
| Powered by | Apache Yetus 0.8.0
[jira] [Comment Edited] (MAPREDUCE-7274) Enable to set running task limit when mapreduce job is running
[
https://issues.apache.org/jira/browse/MAPREDUCE-7274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17084662#comment-17084662
]
Chengwei Wang edited comment on MAPREDUCE-7274 at 4/16/20, 11:15 AM:
-
Upload patch for hadoop 3.2.0.
It enable us to set task running limit when job is running by mapred client
command:
{code:bash}
mapred job -set-running-task-limit JOB_ID TASK_TYPE LIMIT
e.g.
mapred job -set-running-task-limit job_1583809537551_21297 MAP 100
mapred job -set-running-task-limit job_1583809537551_21297 REDUCE 100
{code}
it send a rpc resquest to AM, and AM would update the max running limit of the
specified type task as specified limit count.
was (Author: smarthan):
Upload patch for hadoop 3.2.0.
It enable us to set task running limit when job is running by mapred client
command:
{code:bash}
mapred job -set-running-task-limit JOB_ID TASK_TYPE LIMIT
e.g.
mapred job -set-running-task-limit job_1583809537551_21297 MAP 100
mapred job -set-running-task-limit job_1583809537551_21297 REDUCE 100
{code}
This command would send a rpc resquest to AM, and AM would update the max
running limit of the specified type task as specified limit count.
> Enable to set running task limit when mapreduce job is running
> --
>
> Key: MAPREDUCE-7274
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-7274
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> Components: mr-am, mrv2
>Reporter: Chengwei Wang
>Priority: Major
> Attachments: MAPREDUCE-7274-branch-3.2.0.patch
>
>
> MRv2 enabled users to control the number of map or reduce tasks running
> simultaneously by configuration _mapreduce.job.running.map.limit_ or
> _mapreduce.job.running.reduce.limit._ But users can only set limit number
> before submitting the job to rm. So, it's meaningful to enable users to set
> the limit of running map or reduce tasks when job is running, which can help
> users to restrict resource usage of job and give resources to high-priority
> job.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
[jira] [Commented] (MAPREDUCE-7273) JHS: make sure that Kerberos relogin is performed when KDC becomes offline then online again
[
https://issues.apache.org/jira/browse/MAPREDUCE-7273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17084733#comment-17084733
]
Peter Bacsko commented on MAPREDUCE-7273:
-
[~eyang] thanks, makes perfect sense. I updated the patch.
> JHS: make sure that Kerberos relogin is performed when KDC becomes offline
> then online again
>
>
> Key: MAPREDUCE-7273
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-7273
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: jobhistoryserver
>Affects Versions: 2.10.0, 3.2.1, 3.1.3
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Major
> Attachments: MAPREDUCE-7273-001.patch, MAPREDUCE-7273-002.patch
>
>
> In JHS, if the KDC goes offline, the IPC layer does try to relogin, but it's
> not always enough. You have to wait for 60 seconds for the next retry. In the
> meantime, if the KDC comes back, the following error might occur:
> {noformat}
> 2020-04-09 03:27:52,075 DEBUG ipc.Server (Server.java:processSaslToken(1952))
> - Have read input token of size 708 for processing by
> saslServer.evaluateResponse()
> 2020-04-09 03:27:52,077 DEBUG ipc.Server (Server.java:saslProcess(1829)) -
> javax.security.sasl.SaslException: GSS initiate failed [Caused by
> GSSException: Failure unspecified at GSS-API level (Mechanism level: Invalid
> argument (400) - Cannot find key of appropriate type to decrypt AP REP -
> AES128 CTS mode with HMAC SHA1-96)]
> at
> com.sun.security.sasl.gsskerb.GssKrb5Server.evaluateResponse(GssKrb5Server.java:199)
> ...
> {noformat}
> When this happens, JHS has to be restarted.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
[jira] [Updated] (MAPREDUCE-7273) JHS: make sure that Kerberos relogin is performed when KDC becomes offline then online again
[
https://issues.apache.org/jira/browse/MAPREDUCE-7273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Bacsko updated MAPREDUCE-7273:
Attachment: MAPREDUCE-7273-002.patch
> JHS: make sure that Kerberos relogin is performed when KDC becomes offline
> then online again
>
>
> Key: MAPREDUCE-7273
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-7273
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: jobhistoryserver
>Affects Versions: 2.10.0, 3.2.1, 3.1.3
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Major
> Attachments: MAPREDUCE-7273-001.patch, MAPREDUCE-7273-002.patch
>
>
> In JHS, if the KDC goes offline, the IPC layer does try to relogin, but it's
> not always enough. You have to wait for 60 seconds for the next retry. In the
> meantime, if the KDC comes back, the following error might occur:
> {noformat}
> 2020-04-09 03:27:52,075 DEBUG ipc.Server (Server.java:processSaslToken(1952))
> - Have read input token of size 708 for processing by
> saslServer.evaluateResponse()
> 2020-04-09 03:27:52,077 DEBUG ipc.Server (Server.java:saslProcess(1829)) -
> javax.security.sasl.SaslException: GSS initiate failed [Caused by
> GSSException: Failure unspecified at GSS-API level (Mechanism level: Invalid
> argument (400) - Cannot find key of appropriate type to decrypt AP REP -
> AES128 CTS mode with HMAC SHA1-96)]
> at
> com.sun.security.sasl.gsskerb.GssKrb5Server.evaluateResponse(GssKrb5Server.java:199)
> ...
> {noformat}
> When this happens, JHS has to be restarted.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
[jira] [Updated] (MAPREDUCE-7274) Enable to set running task limit when mapreduce job is running
[ https://issues.apache.org/jira/browse/MAPREDUCE-7274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chengwei Wang updated MAPREDUCE-7274: - Component/s: mrv2 mr-am > Enable to set running task limit when mapreduce job is running > -- > > Key: MAPREDUCE-7274 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-7274 > Project: Hadoop Map/Reduce > Issue Type: New Feature > Components: mr-am, mrv2 >Reporter: Chengwei Wang >Priority: Major > Attachments: MAPREDUCE-7274-branch-3.2.0.patch > > > MRv2 enabled users to control the number of map or reduce tasks running > simultaneously by configuration _mapreduce.job.running.map.limit_ or > _mapreduce.job.running.reduce.limit._ But users can only set limit number > before submitting the job to rm. So, it's meaningful to enable users to set > the limit of running map or reduce tasks when job is running, which can help > users to restrict resource usage of job and give resources to high-priority > job. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
[jira] [Commented] (MAPREDUCE-7274) Enable to set running task limit when mapreduce job is running
[
https://issues.apache.org/jira/browse/MAPREDUCE-7274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17084662#comment-17084662
]
Chengwei Wang commented on MAPREDUCE-7274:
--
Upload patch for hadoop 3.2.0.
It enable us to set task running limit when job is running by mapred client
command:
{code:bash}
mapred job -set-running-task-limit JOB_ID TASK_TYPE LIMIT
e.g.
mapred job -set-running-task-limit job_1583809537551_21297 MAP 100
mapred job -set-running-task-limit job_1583809537551_21297 REDUCE 100
{code}
This command would send a rpc resquest to AM, and AM would update the max
running limit of the specified type task as specified limit count.
> Enable to set running task limit when mapreduce job is running
> --
>
> Key: MAPREDUCE-7274
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-7274
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
>Reporter: Chengwei Wang
>Priority: Major
> Attachments: MAPREDUCE-7274-branch-3.2.0.patch
>
>
> MRv2 enabled users to control the number of map or reduce tasks running
> simultaneously by configuration _mapreduce.job.running.map.limit_ or
> _mapreduce.job.running.reduce.limit._ But users can only set limit number
> before submitting the job to rm. So, it's meaningful to enable users to set
> the limit of running map or reduce tasks when job is running, which can help
> users to restrict resource usage of job and give resources to high-priority
> job.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
[jira] [Comment Edited] (MAPREDUCE-7274) Enable to set running task limit when mapreduce job is running
[ https://issues.apache.org/jira/browse/MAPREDUCE-7274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17084199#comment-17084199 ] Chengwei Wang edited comment on MAPREDUCE-7274 at 4/16/20, 8:04 AM: I would upload a patch for hadoop 2.x or 3.2.0 if needed. was (Author: smarthan): I would upload a patch for hadoop 2.x or 3.2.0 if needed. > Enable to set running task limit when mapreduce job is running > -- > > Key: MAPREDUCE-7274 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-7274 > Project: Hadoop Map/Reduce > Issue Type: New Feature >Reporter: Chengwei Wang >Priority: Major > Attachments: MAPREDUCE-7274-branch-3.2.0.patch > > > MRv2 enabled users to control the number of map or reduce tasks running > simultaneously by configuration _mapreduce.job.running.map.limit_ or > _mapreduce.job.running.reduce.limit._ But users can only set limit number > before submitting the job to rm. So, it's meaningful to enable users to set > the limit of running map or reduce tasks when job is running, which can help > users to restrict resource usage of job and give resources to high-priority > job. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
[jira] [Comment Edited] (MAPREDUCE-7274) Enable to set running task limit when mapreduce job is running
[ https://issues.apache.org/jira/browse/MAPREDUCE-7274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17084199#comment-17084199 ] Chengwei Wang edited comment on MAPREDUCE-7274 at 4/16/20, 8:03 AM: I would upload a patch for hadoop 2.x or 3.2.0 if needed. was (Author: smarthan): I would upload a patch based on hadoop 2.x if needed. > Enable to set running task limit when mapreduce job is running > -- > > Key: MAPREDUCE-7274 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-7274 > Project: Hadoop Map/Reduce > Issue Type: New Feature >Reporter: Chengwei Wang >Priority: Major > Attachments: MAPREDUCE-7274-branch-3.2.0.patch > > > MRv2 enabled users to control the number of map or reduce tasks running > simultaneously by configuration _mapreduce.job.running.map.limit_ or > _mapreduce.job.running.reduce.limit._ But users can only set limit number > before submitting the job to rm. So, it's meaningful to enable users to set > the limit of running map or reduce tasks when job is running, which can help > users to restrict resource usage of job and give resources to high-priority > job. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
[jira] [Updated] (MAPREDUCE-7274) Enable to set running task limit when mapreduce job is running
[ https://issues.apache.org/jira/browse/MAPREDUCE-7274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chengwei Wang updated MAPREDUCE-7274: - Attachment: MAPREDUCE-7274-branch-3.2.0.patch > Enable to set running task limit when mapreduce job is running > -- > > Key: MAPREDUCE-7274 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-7274 > Project: Hadoop Map/Reduce > Issue Type: New Feature >Reporter: Chengwei Wang >Priority: Major > Attachments: MAPREDUCE-7274-branch-3.2.0.patch > > > MRv2 enabled users to control the number of map or reduce tasks running > simultaneously by configuration _mapreduce.job.running.map.limit_ or > _mapreduce.job.running.reduce.limit._ But users can only set limit number > before submitting the job to rm. So, it's meaningful to enable users to set > the limit of running map or reduce tasks when job is running, which can help > users to restrict resource usage of job and give resources to high-priority > job. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
