[jira] [Commented] (HADOOP-12924) Configure raw erasure coders for supported codecs
[
https://issues.apache.org/jira/browse/HADOOP-12924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15245306#comment-15245306
]
Hadoop QA commented on HADOOP-12924:
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 9s
{color} | {color:blue} Docker mode activated. {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:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s {color} | {color:green} The patch appears to include 7 new or modified test
files. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m 13s
{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 6m
31s {color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 5m 39s
{color} | {color:green} trunk passed with JDK v1.8.0_77 {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 6m 45s
{color} | {color:green} trunk passed with JDK v1.7.0_95 {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
5s {color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 2m 21s
{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
40s {color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 5m 9s
{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 2m 16s
{color} | {color:green} trunk passed with JDK v1.8.0_77 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 3m 12s
{color} | {color:green} trunk passed with JDK v1.7.0_95 {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m 14s
{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 1m
58s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 5m 40s
{color} | {color:green} the patch passed with JDK v1.8.0_77 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 5m 40s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 6m 39s
{color} | {color:green} the patch passed with JDK v1.7.0_95 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 6m 39s
{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red} 1m 6s
{color} | {color:red} root: patch generated 1 new + 127 unchanged - 0 fixed =
128 total (was 127) {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 2m 22s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
39s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} Patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} xml {color} | {color:green} 0m 1s
{color} | {color:green} The patch has no ill-formed XML file. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 5m
55s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 2m 16s
{color} | {color:green} the patch passed with JDK v1.8.0_77 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 3m 18s
{color} | {color:green} the patch passed with JDK v1.7.0_95 {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 8m 3s
{color} | {color:green} hadoop-common in the patch passed with JDK v1.8.0_77.
{color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m 53s
{color} | {color:green} hadoop-hdfs-client in the patch passed with JDK
v1.8.0_77. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 55m 10s {color}
| {color:red} hadoop-hdfs in the patch failed with JDK v1.8.0_77. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 8m 25s
{color} | {color:green} hadoop-common in the patch passed with JDK v1.7.0_95.
{color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 1m 0s
{color} | {color:green} hadoop-hdfs-clien
[jira] [Updated] (HADOOP-5470) RunJar.unJar() should write the last modified time found in the jar entry to the uncompressed file
[ https://issues.apache.org/jira/browse/HADOOP-5470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andras Bokor updated HADOOP-5470: - Attachment: HADOOP-5470.03.patch Adding [^HADOOP-5470.03.patch] to eliminate checkstyle warning. > RunJar.unJar() should write the last modified time found in the jar entry to > the uncompressed file > -- > > Key: HADOOP-5470 > URL: https://issues.apache.org/jira/browse/HADOOP-5470 > Project: Hadoop Common > Issue Type: Improvement > Components: util >Affects Versions: 0.18.0, 0.18.1, 0.18.2, 0.18.3, 0.19.0, 0.19.1 >Reporter: Colin Evans >Assignee: Andras Bokor >Priority: Minor > Labels: newbie > Attachments: HADOOP-5470.01.patch, HADOOP-5470.02.patch, > HADOOP-5470.03.patch > > > For tools like jruby and jython, last modified times determine if a script > gets recompiled. Losing the correct last modified time causes some > unfortunate recompilation race conditions when a job is running. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HADOOP-13033) Add missing Javadoc enries to Interns.java
Andras Bokor created HADOOP-13033: - Summary: Add missing Javadoc enries to Interns.java Key: HADOOP-13033 URL: https://issues.apache.org/jira/browse/HADOOP-13033 Project: Hadoop Common Issue Type: Improvement Components: metrics Reporter: Andras Bokor Assignee: Andras Bokor Priority: Minor Fix For: 2.8.0 Interns.java outputs "Metrics intern cache over flow" warn log for metrics info/tag when the cache reaches the hard-coded limit and the oldest cache is discarded for the first time. I'm thinking this log level can be changed to info because * there is no problem when the oldest cache is removed. if the metrics info/tag is not in the cache, simply create it. * we cannot configure the maximum size of the cache, so there is no way to stop the warn log. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HADOOP-13033) Add missing Javadoc enries to Interns.java
[ https://issues.apache.org/jira/browse/HADOOP-13033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andras Bokor updated HADOOP-13033: -- Description: (was: Interns.java outputs "Metrics intern cache over flow" warn log for metrics info/tag when the cache reaches the hard-coded limit and the oldest cache is discarded for the first time. I'm thinking this log level can be changed to info because * there is no problem when the oldest cache is removed. if the metrics info/tag is not in the cache, simply create it. * we cannot configure the maximum size of the cache, so there is no way to stop the warn log.) > Add missing Javadoc enries to Interns.java > -- > > Key: HADOOP-13033 > URL: https://issues.apache.org/jira/browse/HADOOP-13033 > Project: Hadoop Common > Issue Type: Improvement > Components: metrics >Reporter: Andras Bokor >Assignee: Andras Bokor >Priority: Minor > Labels: newbie > Fix For: 2.8.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-12924) Configure raw erasure coders for supported codecs
[ https://issues.apache.org/jira/browse/HADOOP-12924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15245356#comment-15245356 ] Kai Zheng commented on HADOOP-12924: I added the missed package-info.java in HADOOP-13010. The failed tests are not relevant. Will commit this tomorrow if no other comments. > Configure raw erasure coders for supported codecs > - > > Key: HADOOP-12924 > URL: https://issues.apache.org/jira/browse/HADOOP-12924 > Project: Hadoop Common > Issue Type: Sub-task >Reporter: Rui Li >Assignee: Rui Li >Priority: Minor > Labels: hdfs-ec-3.0-must-do > Attachments: HADOOP-12924.1.patch, HADOOP-12924.2.patch, > HADOOP-12924.3.patch, HADOOP-12924.4.patch, HADOOP-12924.5.patch, > HADOOP-12924.6.patch, HADOOP-12924.6.patch > > > As suggested > [here|https://issues.apache.org/jira/browse/HADOOP-12826?focusedCommentId=15194402&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15194402]. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HADOOP-13033) Add missing Javadoc enries to Interns.java
[ https://issues.apache.org/jira/browse/HADOOP-13033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andras Bokor updated HADOOP-13033: -- Attachment: HADOOP-13033.01.patch > Add missing Javadoc enries to Interns.java > -- > > Key: HADOOP-13033 > URL: https://issues.apache.org/jira/browse/HADOOP-13033 > Project: Hadoop Common > Issue Type: Improvement > Components: metrics >Reporter: Andras Bokor >Assignee: Andras Bokor >Priority: Minor > Labels: newbie > Fix For: 2.8.0 > > Attachments: HADOOP-13033.01.patch > > > Interns.java:info(String name, String description) method misses the > description of parameters. With adding the missing entries the will have no > warnings at all. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HADOOP-13033) Add missing Javadoc enries to Interns.java
[ https://issues.apache.org/jira/browse/HADOOP-13033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andras Bokor updated HADOOP-13033: -- Description: Interns.java:info(String name, String description) method misses the description of parameters. With adding the missing entries the will have no warnings at all. > Add missing Javadoc enries to Interns.java > -- > > Key: HADOOP-13033 > URL: https://issues.apache.org/jira/browse/HADOOP-13033 > Project: Hadoop Common > Issue Type: Improvement > Components: metrics >Reporter: Andras Bokor >Assignee: Andras Bokor >Priority: Minor > Labels: newbie > Fix For: 2.8.0 > > Attachments: HADOOP-13033.01.patch > > > Interns.java:info(String name, String description) method misses the > description of parameters. With adding the missing entries the will have no > warnings at all. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HADOOP-13033) Add missing Javadoc enries to Interns.java
[ https://issues.apache.org/jira/browse/HADOOP-13033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andras Bokor updated HADOOP-13033: -- Status: Patch Available (was: Open) > Add missing Javadoc enries to Interns.java > -- > > Key: HADOOP-13033 > URL: https://issues.apache.org/jira/browse/HADOOP-13033 > Project: Hadoop Common > Issue Type: Improvement > Components: metrics >Reporter: Andras Bokor >Assignee: Andras Bokor >Priority: Minor > Labels: newbie > Fix For: 2.8.0 > > Attachments: HADOOP-13033.01.patch > > > Interns.java:info(String name, String description) method misses the > description of parameters. With adding the missing entries the will have no > warnings at all. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-5470) RunJar.unJar() should write the last modified time found in the jar entry to the uncompressed file
[
https://issues.apache.org/jira/browse/HADOOP-5470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15245424#comment-15245424
]
Hadoop QA commented on HADOOP-5470:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 9s
{color} | {color:blue} Docker mode activated. {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:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s {color} | {color:green} The patch appears to include 1 new or modified test
files. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 6m
31s {color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 5m 45s
{color} | {color:green} trunk passed with JDK v1.8.0_77 {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 6m 48s
{color} | {color:green} trunk passed with JDK v1.7.0_95 {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 57s
{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
13s {color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
37s {color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 54s
{color} | {color:green} trunk passed with JDK v1.8.0_77 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m 3s
{color} | {color:green} trunk passed with JDK v1.7.0_95 {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
44s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 6m 15s
{color} | {color:green} the patch passed with JDK v1.8.0_77 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 6m 15s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 6m 39s
{color} | {color:green} the patch passed with JDK v1.7.0_95 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 6m 39s
{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red} 0m 20s
{color} | {color:red} hadoop-common-project/hadoop-common: patch generated 1
new + 5 unchanged - 0 fixed = 6 total (was 5) {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m 57s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
14s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} Patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
48s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 50s
{color} | {color:green} the patch passed with JDK v1.8.0_77 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m 3s
{color} | {color:green} the patch passed with JDK v1.7.0_95 {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 16m 51s {color}
| {color:red} hadoop-common in the patch failed with JDK v1.8.0_77. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 8m 5s
{color} | {color:green} hadoop-common in the patch passed with JDK v1.7.0_95.
{color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
21s {color} | {color:green} Patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 69m 31s {color}
| {color:black} {color} |
\\
\\
|| Reason || Tests ||
| JDK v1.8.0_77 Timed out junit tests |
org.apache.hadoop.http.TestHttpServerLifecycle |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Image:yetus/hadoop:fbe3e86 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12799218/HADOOP-5470.03.patch |
| JIRA Issue | HADOOP-5470 |
| Optional Tests | asflicense compile javac javadoc mvninstall mvnsite
unit findbugs checkstyle |
| uname | Linux 1f1aff23a2a4 3.13.0-36-lowlatency #63-Ubuntu SMP PREEMPT Wed
Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Pers
[jira] [Commented] (HADOOP-13033) Add missing Javadoc enries to Interns.java
[
https://issues.apache.org/jira/browse/HADOOP-13033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15245454#comment-15245454
]
Hadoop QA commented on HADOOP-13033:
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 11m 23s
{color} | {color:blue} Docker mode activated. {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:green}+1{color} | {color:green} mvninstall {color} | {color:green} 6m
48s {color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 5m 34s
{color} | {color:green} trunk passed with JDK v1.8.0_77 {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 6m 32s
{color} | {color:green} trunk passed with JDK v1.7.0_95 {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 57s
{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
14s {color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
33s {color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 51s
{color} | {color:green} trunk passed with JDK v1.8.0_77 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m 1s
{color} | {color:green} trunk passed with JDK v1.7.0_95 {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
40s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 5m 32s
{color} | {color:green} the patch passed with JDK v1.8.0_77 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 5m 32s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 6m 30s
{color} | {color:green} the patch passed with JDK v1.7.0_95 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 6m 30s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
21s {color} | {color:green} hadoop-common-project/hadoop-common: patch
generated 0 new + 3 unchanged - 4 fixed = 3 total (was 7) {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m 56s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
14s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} Patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
47s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 52s
{color} | {color:green} the patch passed with JDK v1.8.0_77 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m 4s
{color} | {color:green} the patch passed with JDK v1.7.0_95 {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 7m 23s
{color} | {color:green} hadoop-common in the patch passed with JDK v1.8.0_77.
{color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 7m 37s
{color} | {color:green} hadoop-common in the patch passed with JDK v1.7.0_95.
{color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
24s {color} | {color:green} Patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 69m 39s {color}
| {color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Image:yetus/hadoop:fbe3e86 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12799220/HADOOP-13033.01.patch
|
| JIRA Issue | HADOOP-13033 |
| Optional Tests | asflicense compile javac javadoc mvninstall mvnsite
unit findbugs checkstyle |
| uname | Linux c81e613cc3a0 3.13.0-36-lowlatency #63-Ubuntu SMP PREEMPT Wed
Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Li
[jira] [Commented] (HADOOP-13010) Refactor raw erasure coders
[ https://issues.apache.org/jira/browse/HADOOP-13010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15245612#comment-15245612 ] Kai Zheng commented on HADOOP-13010: Thanks Colin. bq. It sounds like Encoder and Decoder will be stateless once they're created. Basically, they just reflect an algorithm and some data required to implement that algorithm. That is reasonable. We should document this in the JavaDoc for the classes. Yeah, it's good to document this stateless property in JavaDoc. Note by the way it doesn't mean these encoder/decoder are to support concurrency though it's possible. I would leave this for future consideration. bq. The problem with calling this class DecoderState is that this name suggests that it is the state of the coder, rather than state manipulated by the coder. Perhaps calling this DecoderData or DecoderStream is more appropriate. Having this new class will also avoid the need to manually pass around so many arrays and indices. Ah yes the names (EncoderState/DecoderState) are bad, actually I meant them to be *EncodingState/DecodingState*. bq. These methods and fields are configuration methods and configuration fields. They belong in a class named something like "ErasureEncodingConfiguration" or something like that. ...Why is having the configuration in a separate object better than having the configuration in a base class? Ok, I'm probably convinced by you. Thanks for the lots of insights. I got rid of the base class anyway, and introduced *ErasureCoderConf* for the variables and methods in it. As you might check the updated patch, there are some duplicate of small shortcuts between the encoder base class and decoder base class as they now lack a common base. I suppose it's acceptable. > Refactor raw erasure coders > --- > > Key: HADOOP-13010 > URL: https://issues.apache.org/jira/browse/HADOOP-13010 > Project: Hadoop Common > Issue Type: Sub-task >Reporter: Kai Zheng >Assignee: Kai Zheng > Fix For: 3.0.0 > > Attachments: HADOOP-13010-v1.patch, HADOOP-13010-v2.patch, > HADOOP-13010-v3.patch > > > This will refactor raw erasure coders according to some comments received so > far. > * As discussed in HADOOP-11540 and suggested by [~cmccabe], better not to > rely class inheritance to reuse the codes, instead they can be moved to some > utility. > * Suggested by [~jingzhao] somewhere quite some time ago, better to have a > state holder to keep some checking results for later reuse during an > encode/decode call. > This would not get rid of some inheritance levels as doing so isn't clear yet > for the moment and also incurs big impact. I do wish the end result by this > refactoring will make all the levels more clear and easier to follow. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HADOOP-13034) Log message about input options in distcp lacks some items
Takashi Ohnishi created HADOOP-13034:
Summary: Log message about input options in distcp lacks some items
Key: HADOOP-13034
URL: https://issues.apache.org/jira/browse/HADOOP-13034
Project: Hadoop Common
Issue Type: Improvement
Components: tools/distcp
Affects Versions: 3.0.0
Reporter: Takashi Ohnishi
Priority: Minor
The log message in running distcp does not show some options, i.e. append,
useDiff and snapshot names.
{code}
16/04/18 21:57:36 INFO tools.DistCp: Input Options:
DistCpOptions{atomicCommit=false, syncFolder=true, deleteMissing=false,
ignoreFailures=false, overwrite=false, skipCRC=false, blocking=true,
numListstatusThreads=0, maxMaps=20, mapBandwidth=100.0,
copyStrategy='uniformsize', preserveStatus=[], preserveRawXattrs=false,
atomicWorkPath=null, logPath=null, sourceFileListing=null,
sourcePaths=[/user/hadoop/source], targetPath=/user/hadoop/target,
targetPathExists=true, filtersFile='null'}
{code}
I think that this message is useful for debugging and so it is better to add
the lacked options.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HADOOP-13034) Log message about input options in distcp lacks some items
[
https://issues.apache.org/jira/browse/HADOOP-13034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Takashi Ohnishi updated HADOOP-13034:
-
Status: Patch Available (was: Open)
> Log message about input options in distcp lacks some items
> --
>
> Key: HADOOP-13034
> URL: https://issues.apache.org/jira/browse/HADOOP-13034
> Project: Hadoop Common
> Issue Type: Improvement
> Components: tools/distcp
>Affects Versions: 3.0.0
>Reporter: Takashi Ohnishi
>Priority: Minor
> Attachments: HADOOP-13034.1.patch
>
>
> The log message in running distcp does not show some options, i.e. append,
> useDiff and snapshot names.
> {code}
> 16/04/18 21:57:36 INFO tools.DistCp: Input Options:
> DistCpOptions{atomicCommit=false, syncFolder=true, deleteMissing=false,
> ignoreFailures=false, overwrite=false, skipCRC=false, blocking=true,
> numListstatusThreads=0, maxMaps=20, mapBandwidth=100.0,
> copyStrategy='uniformsize', preserveStatus=[], preserveRawXattrs=false,
> atomicWorkPath=null, logPath=null, sourceFileListing=null,
> sourcePaths=[/user/hadoop/source], targetPath=/user/hadoop/target,
> targetPathExists=true, filtersFile='null'}
> {code}
> I think that this message is useful for debugging and so it is better to add
> the lacked options.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HADOOP-13034) Log message about input options in distcp lacks some items
[
https://issues.apache.org/jira/browse/HADOOP-13034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Takashi Ohnishi updated HADOOP-13034:
-
Attachment: HADOOP-13034.1.patch
Attached patch.
> Log message about input options in distcp lacks some items
> --
>
> Key: HADOOP-13034
> URL: https://issues.apache.org/jira/browse/HADOOP-13034
> Project: Hadoop Common
> Issue Type: Improvement
> Components: tools/distcp
>Affects Versions: 3.0.0
>Reporter: Takashi Ohnishi
>Priority: Minor
> Attachments: HADOOP-13034.1.patch
>
>
> The log message in running distcp does not show some options, i.e. append,
> useDiff and snapshot names.
> {code}
> 16/04/18 21:57:36 INFO tools.DistCp: Input Options:
> DistCpOptions{atomicCommit=false, syncFolder=true, deleteMissing=false,
> ignoreFailures=false, overwrite=false, skipCRC=false, blocking=true,
> numListstatusThreads=0, maxMaps=20, mapBandwidth=100.0,
> copyStrategy='uniformsize', preserveStatus=[], preserveRawXattrs=false,
> atomicWorkPath=null, logPath=null, sourceFileListing=null,
> sourcePaths=[/user/hadoop/source], targetPath=/user/hadoop/target,
> targetPathExists=true, filtersFile='null'}
> {code}
> I think that this message is useful for debugging and so it is better to add
> the lacked options.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (HADOOP-13034) Log message about input options in distcp lacks some items
[
https://issues.apache.org/jira/browse/HADOOP-13034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Takashi Ohnishi reassigned HADOOP-13034:
Assignee: Takashi Ohnishi
> Log message about input options in distcp lacks some items
> --
>
> Key: HADOOP-13034
> URL: https://issues.apache.org/jira/browse/HADOOP-13034
> Project: Hadoop Common
> Issue Type: Improvement
> Components: tools/distcp
>Affects Versions: 3.0.0
>Reporter: Takashi Ohnishi
>Assignee: Takashi Ohnishi
>Priority: Minor
> Attachments: HADOOP-13034.1.patch
>
>
> The log message in running distcp does not show some options, i.e. append,
> useDiff and snapshot names.
> {code}
> 16/04/18 21:57:36 INFO tools.DistCp: Input Options:
> DistCpOptions{atomicCommit=false, syncFolder=true, deleteMissing=false,
> ignoreFailures=false, overwrite=false, skipCRC=false, blocking=true,
> numListstatusThreads=0, maxMaps=20, mapBandwidth=100.0,
> copyStrategy='uniformsize', preserveStatus=[], preserveRawXattrs=false,
> atomicWorkPath=null, logPath=null, sourceFileListing=null,
> sourcePaths=[/user/hadoop/source], targetPath=/user/hadoop/target,
> targetPathExists=true, filtersFile='null'}
> {code}
> I think that this message is useful for debugging and so it is better to add
> the lacked options.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HADOOP-13033) Add missing Javadoc enries to Interns.java
[ https://issues.apache.org/jira/browse/HADOOP-13033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andras Bokor updated HADOOP-13033: -- Attachment: HADOOP-5470.04.patch > Add missing Javadoc enries to Interns.java > -- > > Key: HADOOP-13033 > URL: https://issues.apache.org/jira/browse/HADOOP-13033 > Project: Hadoop Common > Issue Type: Improvement > Components: metrics >Reporter: Andras Bokor >Assignee: Andras Bokor >Priority: Minor > Labels: newbie > Fix For: 2.8.0 > > Attachments: HADOOP-13033.01.patch > > > Interns.java:info(String name, String description) method misses the > description of parameters. With adding the missing entries the will have no > warnings at all. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HADOOP-13033) Add missing Javadoc enries to Interns.java
[ https://issues.apache.org/jira/browse/HADOOP-13033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andras Bokor updated HADOOP-13033: -- Attachment: (was: HADOOP-5470.04.patch) > Add missing Javadoc enries to Interns.java > -- > > Key: HADOOP-13033 > URL: https://issues.apache.org/jira/browse/HADOOP-13033 > Project: Hadoop Common > Issue Type: Improvement > Components: metrics >Reporter: Andras Bokor >Assignee: Andras Bokor >Priority: Minor > Labels: newbie > Fix For: 2.8.0 > > Attachments: HADOOP-13033.01.patch > > > Interns.java:info(String name, String description) method misses the > description of parameters. With adding the missing entries the will have no > warnings at all. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HADOOP-5470) RunJar.unJar() should write the last modified time found in the jar entry to the uncompressed file
[ https://issues.apache.org/jira/browse/HADOOP-5470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andras Bokor updated HADOOP-5470: - Attachment: HADOOP-5470.04.patch > RunJar.unJar() should write the last modified time found in the jar entry to > the uncompressed file > -- > > Key: HADOOP-5470 > URL: https://issues.apache.org/jira/browse/HADOOP-5470 > Project: Hadoop Common > Issue Type: Improvement > Components: util >Affects Versions: 0.18.0, 0.18.1, 0.18.2, 0.18.3, 0.19.0, 0.19.1 >Reporter: Colin Evans >Assignee: Andras Bokor >Priority: Minor > Labels: newbie > Attachments: HADOOP-5470.01.patch, HADOOP-5470.02.patch, > HADOOP-5470.03.patch, HADOOP-5470.04.patch > > > For tools like jruby and jython, last modified times determine if a script > gets recompiled. Losing the correct last modified time causes some > unfortunate recompilation race conditions when a job is running. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Moved] (HADOOP-13035) AbstractService should set state only after state change
[
https://issues.apache.org/jira/browse/HADOOP-13035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Naganarasimha G R moved YARN-4967 to HADOOP-13035:
--
Key: HADOOP-13035 (was: YARN-4967)
Project: Hadoop Common (was: Hadoop YARN)
> AbstractService should set state only after state change
>
>
> Key: HADOOP-13035
> URL: https://issues.apache.org/jira/browse/HADOOP-13035
> Project: Hadoop Common
> Issue Type: Bug
>Reporter: Bibin A Chundatt
>
> As per the discussion in YARN-3971 the we should be setting the service state
> to STARTED only after serviceStart()
> Currently {{AbstractService#start()}} is set
> {noformat}
> if (stateModel.enterState(STATE.STARTED) != STATE.STARTED) {
> try {
> startTime = System.currentTimeMillis();
> serviceStart();
> ..
> }
> {noformat}
> enterState sets the service state to proposed state. So in
> {{service.getServiceState}} in {{serviceStart()}} will return STARTED .
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-13035) AbstractService should set state only after state change
[
https://issues.apache.org/jira/browse/HADOOP-13035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15245676#comment-15245676
]
Naganarasimha G R commented on HADOOP-13035:
Hi [~bibinchundatt], if you have a patch for this, please upload so that we can
cross verify how many failures and evaluate the risk with this change.
> AbstractService should set state only after state change
>
>
> Key: HADOOP-13035
> URL: https://issues.apache.org/jira/browse/HADOOP-13035
> Project: Hadoop Common
> Issue Type: Bug
>Reporter: Bibin A Chundatt
>
> As per the discussion in YARN-3971 the we should be setting the service state
> to STARTED only after serviceStart()
> Currently {{AbstractService#start()}} is set
> {noformat}
> if (stateModel.enterState(STATE.STARTED) != STATE.STARTED) {
> try {
> startTime = System.currentTimeMillis();
> serviceStart();
> ..
> }
> {noformat}
> enterState sets the service state to proposed state. So in
> {{service.getServiceState}} in {{serviceStart()}} will return STARTED .
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-13033) Add missing Javadoc enries to Interns.java
[ https://issues.apache.org/jira/browse/HADOOP-13033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15245695#comment-15245695 ] Andras Bokor commented on HADOOP-13033: --- [~ajisakaa] Can you review this ticket/patch? Thanks in advance. > Add missing Javadoc enries to Interns.java > -- > > Key: HADOOP-13033 > URL: https://issues.apache.org/jira/browse/HADOOP-13033 > Project: Hadoop Common > Issue Type: Improvement > Components: metrics >Reporter: Andras Bokor >Assignee: Andras Bokor >Priority: Minor > Labels: newbie > Fix For: 2.8.0 > > Attachments: HADOOP-13033.01.patch > > > Interns.java:info(String name, String description) method misses the > description of parameters. With adding the missing entries the will have no > warnings at all. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-13034) Log message about input options in distcp lacks some items
[
https://issues.apache.org/jira/browse/HADOOP-13034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15245705#comment-15245705
]
Hadoop QA commented on HADOOP-13034:
| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 15s
{color} | {color:blue} Docker mode activated. {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:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s {color} | {color:green} The patch appears to include 1 new or modified test
files. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 9m
41s {color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 28s
{color} | {color:green} trunk passed with JDK v1.8.0_77 {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 25s
{color} | {color:green} trunk passed with JDK v1.7.0_95 {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
22s {color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m 32s
{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
21s {color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m
41s {color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 24s
{color} | {color:green} trunk passed with JDK v1.8.0_77 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 22s
{color} | {color:green} trunk passed with JDK v1.7.0_95 {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
24s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 23s
{color} | {color:green} the patch passed with JDK v1.8.0_77 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 23s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 22s
{color} | {color:green} the patch passed with JDK v1.7.0_95 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 22s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
16s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m 27s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
15s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} Patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m
52s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 20s
{color} | {color:green} the patch passed with JDK v1.8.0_77 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 18s
{color} | {color:green} the patch passed with JDK v1.7.0_95 {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 10m 41s
{color} | {color:green} hadoop-distcp in the patch passed with JDK v1.8.0_77.
{color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 9m 54s
{color} | {color:green} hadoop-distcp in the patch passed with JDK v1.7.0_95.
{color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
29s {color} | {color:green} Patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 39m 39s {color}
| {color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Image:yetus/hadoop:fbe3e86 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12799247/HADOOP-13034.1.patch |
| JIRA Issue | HADOOP-13034 |
| Optional Tests | asflicense compile javac javadoc mvninstall mvnsite
unit findbugs checkstyle |
| uname | Linux 45af45862b20 3.13.0-36-lowlatency #63-Ubuntu SMP PREEMPT Wed
Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | /testptch/hadoop/patchprocess/precommit/personality/provided.sh
|
| git revision | trunk / d8b729e |
| Default Java | 1.7.0_95 |
| Multi-JDK versions | /usr/lib/jvm
[jira] [Commented] (HADOOP-5470) RunJar.unJar() should write the last modified time found in the jar entry to the uncompressed file
[
https://issues.apache.org/jira/browse/HADOOP-5470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15245795#comment-15245795
]
Hadoop QA commented on HADOOP-5470:
---
| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 9s
{color} | {color:blue} Docker mode activated. {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:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s {color} | {color:green} The patch appears to include 1 new or modified test
files. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 6m
48s {color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 5m 52s
{color} | {color:green} trunk passed with JDK v1.8.0_77 {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 6m 49s
{color} | {color:green} trunk passed with JDK v1.7.0_95 {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 57s
{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
14s {color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
36s {color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 54s
{color} | {color:green} trunk passed with JDK v1.8.0_77 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m 4s
{color} | {color:green} trunk passed with JDK v1.7.0_95 {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
41s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 5m 47s
{color} | {color:green} the patch passed with JDK v1.8.0_77 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 5m 47s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 6m 51s
{color} | {color:green} the patch passed with JDK v1.7.0_95 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 6m 51s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
21s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m 58s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
13s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} Patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
51s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 55s
{color} | {color:green} the patch passed with JDK v1.8.0_77 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m 4s
{color} | {color:green} the patch passed with JDK v1.7.0_95 {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 7m 47s
{color} | {color:green} hadoop-common in the patch passed with JDK v1.8.0_77.
{color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 8m 20s
{color} | {color:green} hadoop-common in the patch passed with JDK v1.7.0_95.
{color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
22s {color} | {color:green} Patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 61m 3s {color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Image:yetus/hadoop:fbe3e86 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12799250/HADOOP-5470.04.patch |
| JIRA Issue | HADOOP-5470 |
| Optional Tests | asflicense compile javac javadoc mvninstall mvnsite
unit findbugs checkstyle |
| uname | Linux 27cd0fed3a98 3.13.0-36-lowlatency #63-Ubuntu SMP PREEMPT Wed
Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | /testptch/hadoop/patchprocess/precommit/personality/provided.sh
|
| git revision | trunk / d8b729e |
| Default Java | 1.7.0_95 |
| Multi-JDK versions | /usr/lib/jvm/java-8-o
[jira] [Commented] (HADOOP-13029) Have FairCallQueue try all lower priority sub queues before backoff
[
https://issues.apache.org/jira/browse/HADOOP-13029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15245854#comment-15245854
]
Daryn Sharp commented on HADOOP-13029:
--
I've been pondering this very question since upgrading to 2.7. I'm not sure
it's a good idea unless well thought out since the current impl suffers from
some unexpected behaviors.
In our experience an abusive user floods the 1st queue and backoff kicks in for
everyone. Agreed, less than desirable. Bad user decays to a lower queue,
probably floods it too. Depending on job width all queues may fill but decay
is a dampener. Allowing simple spillover for all will allow the bad user to
rapidly fill queues. On the flip-side, w/o spillover, nobody was going to get
those queue slots anyway.
Additionally, total call count is driven up by the backoff rejected calls.
Generally shrinking call percentages of all other users into highest priority
queue. Once the bad users' tasks are all blocked in queues, the incoming call
rate appears lower. They decay back into a lower queue and clog it back up
again.
> Have FairCallQueue try all lower priority sub queues before backoff
> ---
>
> Key: HADOOP-13029
> URL: https://issues.apache.org/jira/browse/HADOOP-13029
> Project: Hadoop Common
> Issue Type: Sub-task
>Reporter: Ming Ma
>
> Currently if FairCallQueue and backoff are enabled, backoff will kick in as
> soon as the assigned sub queue is filled up.
> {noformat}
> /**
>* Put and offer follow the same pattern:
>* 1. Get the assigned priorityLevel from the call by scheduler
>* 2. Get the nth sub-queue matching this priorityLevel
>* 3. delegate the call to this sub-queue.
>*
>* But differ in how they handle overflow:
>* - Put will move on to the next queue until it lands on the last queue
>* - Offer does not attempt other queues on overflow
>*/
> {noformat}
> Seems it is better to try lower priority sub queues when the assigned sub
> queue is full, just like the case when backoff is disabled. This will give
> regular users more opportunities and allow the cluster to be configured with
> smaller call queue length. [~chrili], [~arpitagarwal], what do you think?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HADOOP-13030) KMS startup script failed to handle special characters
[
https://issues.apache.org/jira/browse/HADOOP-13030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xiao Chen updated HADOOP-13030:
---
Attachment: HADOOP-13030.03.patch
Patch 3 adds my first part of comment to the function, for better readability.
> KMS startup script failed to handle special characters
> --
>
> Key: HADOOP-13030
> URL: https://issues.apache.org/jira/browse/HADOOP-13030
> Project: Hadoop Common
> Issue Type: Bug
> Components: kms
>Affects Versions: 2.6.0
>Reporter: Xiao Chen
>Assignee: Xiao Chen
> Attachments: HADOOP-13030-repro.tar.gz, HADOOP-13030.01.patch,
> HADOOP-13030.02.patch, HADOOP-13030.03.patch
>
>
> {{kms.sh}} currently cannot handle special characters.
> {code}
> sed -e 's/_kms_ssl_keystore_pass_/'${KMS_SSL_KEYSTORE_PASS}'/g' \
> -e 's/_kms_ssl_truststore_pass_/'${KMS_SSL_TRUSTSTORE_PASS}'/g' \
> "${HADOOP_CATALINA_HOME}/conf/ssl-server.xml.conf" \
> > "${HADOOP_CATALINA_HOME}/conf/ssl-server.xml"
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-13030) KMS startup script failed to handle special characters
[
https://issues.apache.org/jira/browse/HADOOP-13030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15246168#comment-15246168
]
Hadoop QA commented on HADOOP-13030:
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 10s
{color} | {color:blue} Docker mode activated. {color} |
| {color:blue}0{color} | {color:blue} shelldocs {color} | {color:blue} 0m 4s
{color} | {color:blue} Shelldocs was not available. {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:green}+1{color} | {color:green} mvninstall {color} | {color:green} 6m
46s {color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m 20s
{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m 19s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} shellcheck {color} | {color:green} 0m
9s {color} | {color:green} The applied patch generated 0 new + 90 unchanged - 3
fixed = 90 total (was 93) {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} Patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m 11s
{color} | {color:green} hadoop-kms in the patch passed with JDK v1.8.0_77.
{color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m 14s
{color} | {color:green} hadoop-kms in the patch passed with JDK v1.7.0_95.
{color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
17s {color} | {color:green} Patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 8m 41s {color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Image:yetus/hadoop:fbe3e86 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12799297/HADOOP-13030.03.patch
|
| JIRA Issue | HADOOP-13030 |
| Optional Tests | asflicense mvnsite unit shellcheck shelldocs |
| uname | Linux 2f630927a439 3.13.0-36-lowlatency #63-Ubuntu SMP PREEMPT Wed
Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | /testptch/hadoop/patchprocess/precommit/personality/provided.sh
|
| git revision | trunk / d8b729e |
| shellcheck | v0.4.3 |
| JDK v1.7.0_95 Test Results |
https://builds.apache.org/job/PreCommit-HADOOP-Build/9112/testReport/ |
| modules | C: hadoop-common-project/hadoop-kms U:
hadoop-common-project/hadoop-kms |
| Console output |
https://builds.apache.org/job/PreCommit-HADOOP-Build/9112/console |
| Powered by | Apache Yetus 0.2.0 http://yetus.apache.org |
This message was automatically generated.
> KMS startup script failed to handle special characters
> --
>
> Key: HADOOP-13030
> URL: https://issues.apache.org/jira/browse/HADOOP-13030
> Project: Hadoop Common
> Issue Type: Bug
> Components: kms
>Affects Versions: 2.6.0
>Reporter: Xiao Chen
>Assignee: Xiao Chen
> Attachments: HADOOP-13030-repro.tar.gz, HADOOP-13030.01.patch,
> HADOOP-13030.02.patch, HADOOP-13030.03.patch
>
>
> {{kms.sh}} currently cannot handle special characters.
> {code}
> sed -e 's/_kms_ssl_keystore_pass_/'${KMS_SSL_KEYSTORE_PASS}'/g' \
> -e 's/_kms_ssl_truststore_pass_/'${KMS_SSL_TRUSTSTORE_PASS}'/g' \
> "${HADOOP_CATALINA_HOME}/conf/ssl-server.xml.conf" \
> > "${HADOOP_CATALINA_HOME}/conf/ssl-server.xml"
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-13034) Log message about input options in distcp lacks some items
[
https://issues.apache.org/jira/browse/HADOOP-13034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15246416#comment-15246416
]
Daniel Templeton commented on HADOOP-13034:
---
LGTM. Looks like you got all the ones that were missing.
> Log message about input options in distcp lacks some items
> --
>
> Key: HADOOP-13034
> URL: https://issues.apache.org/jira/browse/HADOOP-13034
> Project: Hadoop Common
> Issue Type: Improvement
> Components: tools/distcp
>Affects Versions: 3.0.0
>Reporter: Takashi Ohnishi
>Assignee: Takashi Ohnishi
>Priority: Minor
> Attachments: HADOOP-13034.1.patch
>
>
> The log message in running distcp does not show some options, i.e. append,
> useDiff and snapshot names.
> {code}
> 16/04/18 21:57:36 INFO tools.DistCp: Input Options:
> DistCpOptions{atomicCommit=false, syncFolder=true, deleteMissing=false,
> ignoreFailures=false, overwrite=false, skipCRC=false, blocking=true,
> numListstatusThreads=0, maxMaps=20, mapBandwidth=100.0,
> copyStrategy='uniformsize', preserveStatus=[], preserveRawXattrs=false,
> atomicWorkPath=null, logPath=null, sourceFileListing=null,
> sourcePaths=[/user/hadoop/source], targetPath=/user/hadoop/target,
> targetPathExists=true, filtersFile='null'}
> {code}
> I think that this message is useful for debugging and so it is better to add
> the lacked options.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-13010) Refactor raw erasure coders
[ https://issues.apache.org/jira/browse/HADOOP-13010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15246913#comment-15246913 ] Colin Patrick McCabe commented on HADOOP-13010: --- bq. Yeah, it's good to document this stateless property in JavaDoc. Note by the way it doesn't mean these encoder/decoder are to support concurrency though it's possible. I would leave this for future consideration. Sure. In that case, we should document that these objects are not guaranteed to be thread-safe, so that there is no confusion. bq. Ah yes the names (EncoderState/DecoderState) are bad, actually I meant them to be EncodingState/DecodingState. OK. bq. Ok, I'm probably convinced by you. Thanks for the lots of insights. I got rid of the base class anyway, and introduced ErasureCoderConf for the variables and methods in it. As you might check the updated patch, there are some duplicate of small shortcuts between the encoder base class and decoder base class as they now lack a common base. I suppose it's acceptable. Great. > Refactor raw erasure coders > --- > > Key: HADOOP-13010 > URL: https://issues.apache.org/jira/browse/HADOOP-13010 > Project: Hadoop Common > Issue Type: Sub-task >Reporter: Kai Zheng >Assignee: Kai Zheng > Fix For: 3.0.0 > > Attachments: HADOOP-13010-v1.patch, HADOOP-13010-v2.patch, > HADOOP-13010-v3.patch > > > This will refactor raw erasure coders according to some comments received so > far. > * As discussed in HADOOP-11540 and suggested by [~cmccabe], better not to > rely class inheritance to reuse the codes, instead they can be moved to some > utility. > * Suggested by [~jingzhao] somewhere quite some time ago, better to have a > state holder to keep some checking results for later reuse during an > encode/decode call. > This would not get rid of some inheritance levels as doing so isn't clear yet > for the moment and also incurs big impact. I do wish the end result by this > refactoring will make all the levels more clear and easier to follow. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-13010) Refactor raw erasure coders
[
https://issues.apache.org/jira/browse/HADOOP-13010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15246922#comment-15246922
]
Colin Patrick McCabe commented on HADOOP-13010:
---
{{ErasureCoderConf#setCoderOption}} / {{ErasureCoderConf#getCoderOption}}: I
don't see why we need to have these. If these options are generic to all
erasure encoders, then they can just go as "regular java fields" like
{{ErasureCoderConf#numDataUnits}}, etc. On the other hand, if these options
only apply to one type of Coder, then they should be stored in the particular
type of coder they apply to.
The usual way to do this is to have your Encoder / Decoder class take a
Configuration object as an argument, and pull out whatever values it needs.
For example, you might have code like this:
{code}
FoobarEncoder(Configuration conf) {
this.coderConf = new ErasureCoderConf(conf);
this.foobarity = conf.getLong("foobarity", 123);
}
{code}
The idea is that things that are specific to a class go in that class, rather
than trying to handle it with casts to and from Object.
Also, mutable configuration is unpleasant (what happens if you call
{{ErasureCoderConf#setCoderOption}} when the Encoder / Decoder has already been
created? It seems like what we actually want to do in this case is not modify
the configuration, but build a new Encoder / Decoder with a new configuration.
> Refactor raw erasure coders
> ---
>
> Key: HADOOP-13010
> URL: https://issues.apache.org/jira/browse/HADOOP-13010
> Project: Hadoop Common
> Issue Type: Sub-task
>Reporter: Kai Zheng
>Assignee: Kai Zheng
> Fix For: 3.0.0
>
> Attachments: HADOOP-13010-v1.patch, HADOOP-13010-v2.patch,
> HADOOP-13010-v3.patch
>
>
> This will refactor raw erasure coders according to some comments received so
> far.
> * As discussed in HADOOP-11540 and suggested by [~cmccabe], better not to
> rely class inheritance to reuse the codes, instead they can be moved to some
> utility.
> * Suggested by [~jingzhao] somewhere quite some time ago, better to have a
> state holder to keep some checking results for later reuse during an
> encode/decode call.
> This would not get rid of some inheritance levels as doing so isn't clear yet
> for the moment and also incurs big impact. I do wish the end result by this
> refactoring will make all the levels more clear and easier to follow.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HADOOP-13035) AbstractService should set state only after state change
[
https://issues.apache.org/jira/browse/HADOOP-13035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bibin A Chundatt updated HADOOP-13035:
--
Attachment: 0001-HADOOP-13035.patch
Attaching patch for the handling the state change of after serviceStart init
and stopped.
> AbstractService should set state only after state change
>
>
> Key: HADOOP-13035
> URL: https://issues.apache.org/jira/browse/HADOOP-13035
> Project: Hadoop Common
> Issue Type: Bug
>Reporter: Bibin A Chundatt
> Attachments: 0001-HADOOP-13035.patch
>
>
> As per the discussion in YARN-3971 the we should be setting the service state
> to STARTED only after serviceStart()
> Currently {{AbstractService#start()}} is set
> {noformat}
> if (stateModel.enterState(STATE.STARTED) != STATE.STARTED) {
> try {
> startTime = System.currentTimeMillis();
> serviceStart();
> ..
> }
> {noformat}
> enterState sets the service state to proposed state. So in
> {{service.getServiceState}} in {{serviceStart()}} will return STARTED .
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HADOOP-13035) AbstractService should set state only after state change
[
https://issues.apache.org/jira/browse/HADOOP-13035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bibin A Chundatt updated HADOOP-13035:
--
Status: Patch Available (was: Open)
> AbstractService should set state only after state change
>
>
> Key: HADOOP-13035
> URL: https://issues.apache.org/jira/browse/HADOOP-13035
> Project: Hadoop Common
> Issue Type: Bug
>Reporter: Bibin A Chundatt
> Attachments: 0001-HADOOP-13035.patch
>
>
> As per the discussion in YARN-3971 the we should be setting the service state
> to STARTED only after serviceStart()
> Currently {{AbstractService#start()}} is set
> {noformat}
> if (stateModel.enterState(STATE.STARTED) != STATE.STARTED) {
> try {
> startTime = System.currentTimeMillis();
> serviceStart();
> ..
> }
> {noformat}
> enterState sets the service state to proposed state. So in
> {{service.getServiceState}} in {{serviceStart()}} will return STARTED .
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (HADOOP-13036) Typo in DistCp documentation.
Takashi Ohnishi created HADOOP-13036: Summary: Typo in DistCp documentation. Key: HADOOP-13036 URL: https://issues.apache.org/jira/browse/HADOOP-13036 Project: Hadoop Common Issue Type: Bug Components: documentation Affects Versions: 3.0.0 Reporter: Takashi Ohnishi Priority: Trivial 'If `mapreduce.map.speculative` is set set final and true' seems to be 'If `mapreduce.map.speculative` is set final and true'. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HADOOP-13036) Typo in DistCp documentation.
[ https://issues.apache.org/jira/browse/HADOOP-13036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Takashi Ohnishi updated HADOOP-13036: - Attachment: HADOOP-13036.1.patch Attached patch. > Typo in DistCp documentation. > - > > Key: HADOOP-13036 > URL: https://issues.apache.org/jira/browse/HADOOP-13036 > Project: Hadoop Common > Issue Type: Bug > Components: documentation >Affects Versions: 3.0.0 >Reporter: Takashi Ohnishi >Priority: Trivial > Attachments: HADOOP-13036.1.patch > > > 'If `mapreduce.map.speculative` is set set final and true' seems to be 'If > `mapreduce.map.speculative` is set final and true'. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HADOOP-13036) Typo in DistCp documentation.
[ https://issues.apache.org/jira/browse/HADOOP-13036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Takashi Ohnishi updated HADOOP-13036: - Status: Patch Available (was: Open) > Typo in DistCp documentation. > - > > Key: HADOOP-13036 > URL: https://issues.apache.org/jira/browse/HADOOP-13036 > Project: Hadoop Common > Issue Type: Bug > Components: documentation >Affects Versions: 3.0.0 >Reporter: Takashi Ohnishi >Priority: Trivial > Attachments: HADOOP-13036.1.patch > > > 'If `mapreduce.map.speculative` is set set final and true' seems to be 'If > `mapreduce.map.speculative` is set final and true'. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-13036) Typo in DistCp documentation.
[
https://issues.apache.org/jira/browse/HADOOP-13036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15247139#comment-15247139
]
Hadoop QA commented on HADOOP-13036:
| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 11s
{color} | {color:blue} Docker mode activated. {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:green}+1{color} | {color:green} mvninstall {color} | {color:green} 6m
30s {color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m 22s
{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m 19s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} Patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
19s {color} | {color:green} Patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 7m 55s {color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Image:yetus/hadoop:fbe3e86 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12799431/HADOOP-13036.1.patch |
| JIRA Issue | HADOOP-13036 |
| Optional Tests | asflicense mvnsite |
| uname | Linux dbe4333e3f5c 3.13.0-36-lowlatency #63-Ubuntu SMP PREEMPT Wed
Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | /testptch/hadoop/patchprocess/precommit/personality/provided.sh
|
| git revision | trunk / be0bce1 |
| modules | C: hadoop-tools/hadoop-distcp U: hadoop-tools/hadoop-distcp |
| Console output |
https://builds.apache.org/job/PreCommit-HADOOP-Build/9114/console |
| Powered by | Apache Yetus 0.2.0 http://yetus.apache.org |
This message was automatically generated.
> Typo in DistCp documentation.
> -
>
> Key: HADOOP-13036
> URL: https://issues.apache.org/jira/browse/HADOOP-13036
> Project: Hadoop Common
> Issue Type: Bug
> Components: documentation
>Affects Versions: 3.0.0
>Reporter: Takashi Ohnishi
>Priority: Trivial
> Attachments: HADOOP-13036.1.patch
>
>
> 'If `mapreduce.map.speculative` is set set final and true' seems to be 'If
> `mapreduce.map.speculative` is set final and true'.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-12911) Upgrade Hadoop MiniKDC with Kerby
[ https://issues.apache.org/jira/browse/HADOOP-12911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15247218#comment-15247218 ] Jiajia Li commented on HADOOP-12911: bq. What's the downstream impact if we do these incompatible changes? I know a lot of downstreams use MiniCluster for instance, and thus perhaps MiniKdc for secure cluster testing. I checked HBase and Ooize, they use these interface methods: createConf(), start(), createPrincipal(), getRealm(), stop(). In this patch, only the conf file in tests is changed, and it incurred no changes of the interface. So I think it will not impact the downstream projects. > Upgrade Hadoop MiniKDC with Kerby > - > > Key: HADOOP-12911 > URL: https://issues.apache.org/jira/browse/HADOOP-12911 > Project: Hadoop Common > Issue Type: Improvement > Components: test >Reporter: Jiajia Li >Assignee: Jiajia Li > Attachments: HADOOP-12911-v1.patch, HADOOP-12911-v2.patch, > HADOOP-12911-v3.patch, HADOOP-12911-v4.patch, HADOOP-12911-v5.patch, > HADOOP-12911-v6.patch > > > As discussed in the mailing list, we’d like to introduce Apache Kerby into > Hadoop. Initially it’s good to start with upgrading Hadoop MiniKDC with Kerby > offerings. Apache Kerby (https://github.com/apache/directory-kerby), as an > Apache Directory sub project, is a Java Kerberos binding. It provides a > SimpleKDC server that borrowed ideas from MiniKDC and implemented all the > facilities existing in MiniKDC. Currently MiniKDC depends on the old Kerberos > implementation in Directory Server project, but the implementation is stopped > being maintained. Directory community has a plan to replace the > implementation using Kerby. MiniKDC can use Kerby SimpleKDC directly to avoid > depending on the full of Directory project. Kerby also provides nice identity > backends such as the lightweight memory based one and the very simple json > one for easy development and test environments. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
