[jira] [Created] (HDDS-2409) CI - acceptance test results link is broken in GitHub

[Istvan Fajth (Jira)]

Istvan Fajth created HDDS-2409:
--

 Summary: CI - acceptance test results link is broken in GitHub
 Key: HDDS-2409
 URL: https://issues.apache.org/jira/browse/HDDS-2409
 Project: Hadoop Distributed Data Store
  Issue Type: Bug
Reporter: Istvan Fajth


When I click to see the acceptance test results in a Pull Request, I get a 404.
It seems elek.github.io is not available, and the link points to there.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org

[jira] [Resolved] (HDDS-2377) Speed up TestOzoneManagerHA#testOMRetryProxy and #testTwoOMNodesDown

[Bharat Viswanadham (Jira)]

 [ 
https://issues.apache.org/jira/browse/HDDS-2377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bharat Viswanadham resolved HDDS-2377.
--
Fix Version/s: 0.5.0
   Resolution: Fixed

> Speed up TestOzoneManagerHA#testOMRetryProxy and #testTwoOMNodesDown
> 
>
> Key: HDDS-2377
> URL: https://issues.apache.org/jira/browse/HDDS-2377
> Project: Hadoop Distributed Data Store
>  Issue Type: Improvement
>Reporter: Siyao Meng
>Assignee: Siyao Meng
>Priority: Major
>  Labels: pull-request-available
> Fix For: 0.5.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Marton's comment:
> https://github.com/apache/hadoop-ozone/pull/30#pullrequestreview-302465440
> Out of curiosity, I ran entire TestOzoneManagerHA locally. The entire test 
> class finished in 10m 30s. I discovered {{testOMRetryProxy}} and 
> {{testTwoOMNodesDown}} are taking the most time (2m and 2m 30s respectively) 
> to finish. Most time are wasted on retry and wait. We could reasonably reduce 
> the amount of time on the wait.
> As I tested, with the patch, {{testOMRetryProxy}} and {{testTwoOMNodesDown}} 
> finish in 20 sec each, saving almost 4 min runtime on those two tests alone. 
> The whole TestOzoneManagerHA test finishes in 5m 44s with the patch.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org

[jira] [Created] (HDFS-14963) Add DFS Client caching active namenode mechanism.

[Xudong Cao (Jira)]

Xudong Cao created HDFS-14963:
-

 Summary: Add DFS Client caching active namenode mechanism.
 Key: HDFS-14963
 URL: https://issues.apache.org/jira/browse/HDFS-14963
 Project: Hadoop HDFS
  Issue Type: Improvement
  Components: hdfs-client
Affects Versions: 3.1.3
Reporter: Xudong Cao
Assignee: Xudong Cao






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org

[jira] [Created] (HDFS-14962) RBF: ConnectionPool#newConnection() error log wrong protocol class

[Yuxuan Wang (Jira)]

Yuxuan Wang created HDFS-14962:
--

 Summary: RBF: ConnectionPool#newConnection() error log wrong 
protocol class
 Key: HDFS-14962
 URL: https://issues.apache.org/jira/browse/HDFS-14962
 Project: Hadoop HDFS
  Issue Type: Bug
  Components: rbf
Affects Versions: 3.3.0
Reporter: Yuxuan Wang
Assignee: Yuxuan Wang


ConnectionPool#newConnection() has following code:
{code:java}
String msg = "Unsupported protocol for connection to NameNode: "
+ ((proto != null) ? proto.getClass().getName() : "null");
{code}
*proto.getClass().getName()* should be *proto.getName()*

My IDE can figure out the issue.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org

Apache Hadoop qbt Report: branch2+JDK7 on Linux/x86

[Apache Jenkins Server]

For more details, see 
https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/498/

[Nov 6, 2019 11:47:57 PM] (shv) HDFS-14941. Potential editlog race condition 
can cause corrupted file.
[Nov 7, 2019 12:23:51 AM] (shv) HDFS-14806. Bootstrap standby may fail if with 
in-progress tailing.

-
To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org

[jira] [Created] (HDFS-14961) TestDFSZKFailoverController fails consistently

[Jira]

Íñigo Goiri created HDFS-14961:
--

 Summary: TestDFSZKFailoverController fails consistently
 Key: HDFS-14961
 URL: https://issues.apache.org/jira/browse/HDFS-14961
 Project: Hadoop HDFS
  Issue Type: Bug
Reporter: Íñigo Goiri


TestDFSZKFailoverController has been consistently failing with a time out 
waiting in testManualFailoverWithDFSHAAdmin(). In particular 
{{waitForHAState(1, HAServiceState.OBSERVER);}}.




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org

[jira] [Created] (HDFS-14960) TesteBalancerWithNodeGroup should not succeed with DFSNetworkTopology

[Jim Brennan (Jira)]

Jim Brennan created HDFS-14960:
--

 Summary: TesteBalancerWithNodeGroup should not succeed with 
DFSNetworkTopology
 Key: HDFS-14960
 URL: https://issues.apache.org/jira/browse/HDFS-14960
 Project: Hadoop HDFS
  Issue Type: Improvement
  Components: hdfs
Affects Versions: 3.1.3
Reporter: Jim Brennan


As reported in HDFS-14958, TestBalancerWithNodeGroup was succeeding even though 
it was using DFSNetworkTopology instead of NetworkTopologyWithNodeGroup.

[~inigoiri] rightly suggested that this indicates the test is not very good - 
it should fail when run without NetworkTopologyWithNodeGroup.

We should improve this test.

 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org

[jira] [Resolved] (HDDS-529) Some Ozone DataNode logs go to a separate ozone.log file

[Arpit Agarwal (Jira)]

 [ 
https://issues.apache.org/jira/browse/HDDS-529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arpit Agarwal resolved HDDS-529.

Resolution: Done

Thanks for the note [~Huachao]. This appears to be fixed now. I no longer see 
log output going to ozone.log file.

> Some Ozone DataNode logs go to a separate ozone.log file
> 
>
> Key: HDDS-529
> URL: https://issues.apache.org/jira/browse/HDDS-529
> Project: Hadoop Distributed Data Store
>  Issue Type: Bug
>  Components: Ozone Datanode
>Reporter: Arpit Agarwal
>Assignee: YiSheng Lien
>Priority: Blocker
>  Labels: beta1
>
> Some, but not all DataNode logs go to a separate ozone.log file. Couple of 
> things to fix here:
> # The behavior should be consistent. All log messages should go to the new 
> log file.
> # The new log file name should follow the Hadoop log file convention e.g. 
> _hadoop---.log_



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org

[jira] [Created] (HDFS-14959) [SBNN read] access time should be turned off

[Wei-Chiu Chuang (Jira)]

Wei-Chiu Chuang created HDFS-14959:
--

 Summary: [SBNN read] access time should be turned off
 Key: HDFS-14959
 URL: https://issues.apache.org/jira/browse/HDFS-14959
 Project: Hadoop HDFS
  Issue Type: Task
  Components: documentation
Reporter: Wei-Chiu Chuang


Both Uber and Didi shared that access time has to be switched off to avoid 
spiky NameNode RPC process time. If access time is not off entirely, 
getBlockLocations RPCs have to update access time and must access the active 
NameNode. (that's my understanding. haven't checked the code)

We should record this as a best practice in our doc.

(If you are on the ASF slack, check out this thread
https://the-asf.slack.com/archives/CAD7C52Q3/p1572033324008600)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org

Re: [VOTE] create ozone-dev and ozone-issues mailing lists

[Arpit Agarwal]

Good idea. Thanks Ayush.

Filed https://issues.apache.org/jira/browse/HADOOP-16688 



> On Nov 6, 2019, at 10:29 AM, Ayush Saxena  wrote:
> 
> Hi,
> Probably we should mention the new lists in the document too. Here :
> https://hadoop.apache.org/mailing_lists.html
> 
> -Ayush
> 
> On Mon, 4 Nov 2019 at 16:19, Elek, Marton  wrote:
> 
>> Thanks Arpit.
>> 
>> Notification rules has also been adjusted (thanks to INFRA).
>> 
>> https://issues.apache.org/jira/browse/INFRA-19378
>> 
>> Marton
>> 
>> On 11/1/19 4:46 PM, Arpit Agarwal wrote:
>>> Thanks for kicking this off Marton. Submitted INFRA requests to create
>> the following. The lists should be live soon.
>>> 
>>>  - ozone-dev@h.a.o
>>>  - ozone-issues@h.a.o
>>>  - ozone-commits@h.a.o
>>> 
>>> 
>>> 
 On Oct 31, 2019, at 3:32 AM, Elek, Marton  wrote:
 
 
 Thanks for all the votes and feedback.
 
 The vote is passed with no -1 and with many +1
 
 The mailing lists will be created soon and the notification settings
>> will be updated.
 
 Thank you for your patience.
 Marton
 
 
 On 10/27/19 9:25 AM, Elek, Marton wrote:
> As discussed earlier in the thread of "Hadoop-Ozone repository mailing
>> list configurations" [1] I suggested to solve the current misconfiguration
>> problem with creating separated mailing lists (dev/issues) for Hadoop Ozone.
> It would have some additional benefit: for example it would make
>> easier to follow the Ozone development and future plans.
> Here I am starting a new vote thread (open for at least 72 hours) to
>> collect more feedback about this.
> Please express your opinion / vote.
> Thanks a lot,
> Marton
> [1]
>> https://lists.apache.org/thread.html/dc66a30f48a744534e748c418bf7ab6275896166ca5ade11560ebaef@%3Chdfs-dev.hadoop.apache.org%3E
>> -
> To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
> For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org
 
 -
 To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
 For additional commands, e-mail: common-dev-h...@hadoop.apache.org
 
>>> 
>>> 
>>> -
>>> To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
>>> For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org
>>> 
>> 
>> -
>> To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
>> For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org
>> 
>> 

Re: [VOTE] create ozone-dev and ozone-issues mailing lists

[Ayush Saxena]

Hi,
Probably we should mention the new lists in the document too. Here :
https://hadoop.apache.org/mailing_lists.html

-Ayush

On Mon, 4 Nov 2019 at 16:19, Elek, Marton  wrote:

> Thanks Arpit.
>
> Notification rules has also been adjusted (thanks to INFRA).
>
> https://issues.apache.org/jira/browse/INFRA-19378
>
> Marton
>
> On 11/1/19 4:46 PM, Arpit Agarwal wrote:
> > Thanks for kicking this off Marton. Submitted INFRA requests to create
> the following. The lists should be live soon.
> >
> >   - ozone-dev@h.a.o
> >   - ozone-issues@h.a.o
> >   - ozone-commits@h.a.o
> >
> >
> >
> >> On Oct 31, 2019, at 3:32 AM, Elek, Marton  wrote:
> >>
> >>
> >> Thanks for all the votes and feedback.
> >>
> >> The vote is passed with no -1 and with many +1
> >>
> >> The mailing lists will be created soon and the notification settings
> will be updated.
> >>
> >> Thank you for your patience.
> >> Marton
> >>
> >>
> >> On 10/27/19 9:25 AM, Elek, Marton wrote:
> >>> As discussed earlier in the thread of "Hadoop-Ozone repository mailing
> list configurations" [1] I suggested to solve the current misconfiguration
> problem with creating separated mailing lists (dev/issues) for Hadoop Ozone.
> >>> It would have some additional benefit: for example it would make
> easier to follow the Ozone development and future plans.
> >>> Here I am starting a new vote thread (open for at least 72 hours) to
> collect more feedback about this.
> >>> Please express your opinion / vote.
> >>> Thanks a lot,
> >>> Marton
> >>> [1]
> https://lists.apache.org/thread.html/dc66a30f48a744534e748c418bf7ab6275896166ca5ade11560ebaef@%3Chdfs-dev.hadoop.apache.org%3E
> -
> >>> To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
> >>> For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org
> >>
> >> -
> >> To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
> >> For additional commands, e-mail: common-dev-h...@hadoop.apache.org
> >>
> >
> >
> > -
> > To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
> > For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org
> >
>
> -
> To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
> For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org
>
>

[jira] [Created] (HDFS-14958) TestBalancerWithNodeGroup is not using NetworkTopologyWithNodeGroup

[Jim Brennan (Jira)]

Jim Brennan created HDFS-14958:
--

 Summary: TestBalancerWithNodeGroup is not using 
NetworkTopologyWithNodeGroup
 Key: HDFS-14958
 URL: https://issues.apache.org/jira/browse/HDFS-14958
 Project: Hadoop HDFS
  Issue Type: Bug
  Components: hdfs
Affects Versions: 3.1.3
Reporter: Jim Brennan


TestBalancerWithNodeGroup is intended to test with 
{{NetworkTopologyWithNodeGroup}}, but it is not configured correctly.  Because 
{{DFSConfigKeys.DFS_USE_DFS_NETWORK_TOPOLOGY_KEY}} defaults to true, 
{{CommonConfigurationKeysPublic.NET_TOPOLOGY_IMPL_KEY}} is ignored and the test 
actually uses the default {{DFSNetworkTopology}}.




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org

[jira] [Created] (HDFS-14957) INodeReference Space Consumed was not same in QuotaUsage and ContentSummary

[hemanthboyina (Jira)]

hemanthboyina created HDFS-14957:


 Summary: INodeReference Space Consumed was not same in QuotaUsage 
and ContentSummary
 Key: HDFS-14957
 URL: https://issues.apache.org/jira/browse/HDFS-14957
 Project: Hadoop HDFS
  Issue Type: Bug
Reporter: hemanthboyina






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org

Apache Hadoop qbt Report: branch2+JDK7 on Linux/x86

[Apache Jenkins Server]

For more details, see 
https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/497/

[Nov 5, 2019 4:03:52 PM] (ericp) YARN-8004. Add unit tests for inter queue 
preemption for dominant
[Nov 5, 2019 9:48:27 PM] (jeagles) MAPREDUCE-7208. Tuning TaskRuntimeEstimator. 
(Ahmed Hussein via jeagles)




-1 overall


The following subsystems voted -1:
asflicense findbugs hadolint pathlen unit xml


The following subsystems voted -1 but
were configured to be filtered/ignored:
cc checkstyle javac javadoc pylint shellcheck shelldocs whitespace


The following subsystems are considered long running:
(runtime bigger than 1h  0m  0s)
unit


Specific tests:

XML :

   Parsing Error(s): 
   
hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/conf/empty-configuration.xml
 
   hadoop-tools/hadoop-azure/src/config/checkstyle-suppressions.xml 
   hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui/public/crossdomain.xml 
   
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui/src/main/webapp/public/crossdomain.xml
 

FindBugs :

   
module:hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-timelineservice-hbase/hadoop-yarn-server-timelineservice-hbase-client
 
   Boxed value is unboxed and then immediately reboxed in 
org.apache.hadoop.yarn.server.timelineservice.storage.common.ColumnRWHelper.readResultsWithTimestamps(Result,
 byte[], byte[], KeyConverter, ValueConverter, boolean) At 
ColumnRWHelper.java:then immediately reboxed in 
org.apache.hadoop.yarn.server.timelineservice.storage.common.ColumnRWHelper.readResultsWithTimestamps(Result,
 byte[], byte[], KeyConverter, ValueConverter, boolean) At 
ColumnRWHelper.java:[line 335] 

Failed junit tests :

   
hadoop.security.authentication.server.TestJWTRedirectAuthenticationHandler 
   hadoop.hdfs.TestWriteRead 
   hadoop.hdfs.qjournal.server.TestJournalNodeRespectsBindHostKeys 
   hadoop.hdfs.TestDFSClientRetries 
   hadoop.hdfs.TestSecureEncryptionZoneWithKMS 
   hadoop.hdfs.server.namenode.ha.TestSeveralNameNodes 
   hadoop.hdfs.TestDataTransferKeepalive 
   hadoop.hdfs.TestDistributedFileSystem 
   hadoop.contrib.bkjournal.TestBookKeeperHACheckpoints 
   hadoop.fs.contract.router.web.TestRouterWebHDFSContractSeek 
   hadoop.fs.contract.router.web.TestRouterWebHDFSContractOpen 
   hadoop.contrib.bkjournal.TestBookKeeperHACheckpoints 
   hadoop.registry.secure.TestSecureLogins 
   hadoop.yarn.server.timelineservice.security.TestTimelineAuthFilterForV2 
  

   cc:

   
https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/497/artifact/out/diff-compile-cc-root-jdk1.7.0_95.txt
  [4.0K]

   javac:

   
https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/497/artifact/out/diff-compile-javac-root-jdk1.7.0_95.txt
  [328K]

   cc:

   
https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/497/artifact/out/diff-compile-cc-root-jdk1.8.0_222.txt
  [4.0K]

   javac:

   
https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/497/artifact/out/diff-compile-javac-root-jdk1.8.0_222.txt
  [308K]

   checkstyle:

   
https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/497/artifact/out/diff-checkstyle-root.txt
  [16M]

   hadolint:

   
https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/497/artifact/out/diff-patch-hadolint.txt
  [4.0K]

   pathlen:

   
https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/497/artifact/out/pathlen.txt
  [12K]

   pylint:

   
https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/497/artifact/out/diff-patch-pylint.txt
  [24K]

   shellcheck:

   
https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/497/artifact/out/diff-patch-shellcheck.txt
  [72K]

   shelldocs:

   
https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/497/artifact/out/diff-patch-shelldocs.txt
  [8.0K]

   whitespace:

   
https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/497/artifact/out/whitespace-eol.txt
  [12M]
   
https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/497/artifact/out/whitespace-tabs.txt
  [1.3M]

   xml:

   
https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/497/artifact/out/xml.txt
  [12K]

   findbugs:

   
https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/497/artifact/out/branch-findbugs-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-timelineservice-hbase_hadoop-yarn-server-timelineservice-hbase-client-warnings.html
  [8.0K]

   javadoc:

   
https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/497/artifact/out/diff-javadoc-javadoc-root-jdk1.7.0_95.txt
  [16K]
   
https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/497/artifact/out/diff-javadoc-javadoc-root-jdk1.8.0_222.txt
  [1.1M]

   unit:

   

[jira] [Created] (HDDS-2408) Separate OM Storage initialization from OzoneManager

[Istvan Fajth (Jira)]

Istvan Fajth created HDDS-2408:
--

 Summary: Separate OM Storage initialization from OzoneManager
 Key: HDDS-2408
 URL: https://issues.apache.org/jira/browse/HDDS-2408
 Project: Hadoop Distributed Data Store
  Issue Type: Sub-task
Reporter: Istvan Fajth


The Ozone Manager Storage initialization is partly using the scm security 
client protocol.

As a first step of cleaning up high level protobuf usage from the code, it is 
beneficial to separate this initialization code, so that it is clearly visible 
what parts of the SCM it is using, and later it helps to figure out the better 
design for the SCM security client related calls.

This JIRA is aiming for the following separation tasks:
- Clear out the OM Storage initialization related code from OzoneManager class
- Clear out and move the common code that is used by OzoneManager class 
initialization and OzoneManager Storage initialization logic to avoid any 
duplication.
- Clear unused stuff from OzoneManager after the changes.
- To be the first step in a longer refactoring activity that clears out the SCM 
client and security client calls related code in OzoneManager and from things 
like KeyManager to have these abstracted from protobuf



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org

[jira] [Created] (HDFS-14956) RBF : Router Safemode status should display properly without any unnecessary time-stamp and info log

[Souryakanta Dwivedy (Jira)]

Souryakanta Dwivedy created HDFS-14956:
--

 Summary: RBF : Router Safemode status should display properly 
without any unnecessary time-stamp and info log
 Key: HDFS-14956
 URL: https://issues.apache.org/jira/browse/HDFS-14956
 Project: Hadoop HDFS
  Issue Type: Improvement
  Components: rbf
Affects Versions: 3.1.1
 Environment: RBF Cluster
Reporter: Souryakanta Dwivedy
 Attachments: RBF_Safemode_log.PNG

Router Safemode status should display properly without any unnecesary 
time-stamp and info log

Step:-
 * Make the Router Safemode On/Off
 *  Get the Safemode info and check the output format

Actual output :- Actual output :-      

 ./hdfs dfsrouteradmin -safemode get2019-11-06 17:00:20,209 INFO 
federation.RouterAdmin: Router 
org.apache.hadoop.hdfs.protocolPB.RouterAdminProtocolTranslatorPB@31304f14 
safemode status : trueSafe Mode: true


Expected Output :-          Router safemode status : true       

                                                               Safe Mode: true



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org

[jira] [Created] (HDFS-14955) RBF: getQuotaUsage() on mount point should return global quota.

[Jinglun (Jira)]

Jinglun created HDFS-14955:
--

 Summary: RBF: getQuotaUsage() on mount point should return global 
quota.
 Key: HDFS-14955
 URL: https://issues.apache.org/jira/browse/HDFS-14955
 Project: Hadoop HDFS
  Issue Type: Improvement
Reporter: Jinglun
Assignee: Jinglun


When getQuotaUsage() on a mount point path, the quota part should be the global 
quota. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org

[jira] [Created] (HDFS-14954) [Dynamometer] create-slim-hadoop-tar.sh accidentally removes junit jar from tarball

[Takanobu Asanuma (Jira)]

Takanobu Asanuma created HDFS-14954:
---

 Summary: [Dynamometer] create-slim-hadoop-tar.sh accidentally 
removes junit jar from tarball
 Key: HDFS-14954
 URL: https://issues.apache.org/jira/browse/HDFS-14954
 Project: Hadoop HDFS
  Issue Type: Sub-task
Reporter: Takanobu Asanuma


JUnit jar path is different each hadoop version.
{noformat}
$ find hadoop-2.9.2 -name "junit*.jar"
hadoop-2.9.2/share/hadoop/common/lib/junit-4.11.jar
hadoop-2.9.2/share/hadoop/mapreduce/lib/junit-4.11.jar
$ find hadoop-3.0.0 -name "junit*.jar"
hadoop-3.0.0/share/hadoop/common/lib/junit-4.11.jar
$ find hadoop-3.1.3 -name "junit*.jar"
hadoop-3.1.3/share/hadoop/mapreduce/lib/junit-4.11.jar
$ find hadoop-3.2.1 -name "junit*.jar"
hadoop-3.2.1/share/hadoop/mapreduce/lib/junit-4.11.jar
$ find hadoop-3.3.0-SNAPSHOT -name "junit*.jar"
hadoop-3.3.0-SNAPSHOT/share/hadoop/tools/lib/junit-4.12.jar
{noformat}
Since {{create-slim-hadoop-tar.sh}} removes the tools directory, the junit jar 
is removed after hadoop-3.1 that is necessary for Dyno-DNs.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org