[jira] [Created] (HDFS-13843) RBF: When we add/update mount entry to multiple destinations, unable to see the order information in mount entry points and in federation router UI

2018-08-21 Thread Soumyapn (JIRA)
Soumyapn created HDFS-13843:
---

 Summary: RBF: When we add/update mount entry to multiple 
destinations, unable to see the order information in mount entry points and in 
federation router UI
 Key: HDFS-13843
 URL: https://issues.apache.org/jira/browse/HDFS-13843
 Project: Hadoop HDFS
  Issue Type: Bug
  Components: federation
Reporter: Soumyapn


*Scenario:*

Execute the below add/update command for single mount entry for single 
nameservice pointing to multiple destinations. 
 # hdfs dfsrouteradmin -add /apps1 hacluster /tmp1
 # hdfs dfsrouteradmin -add /apps1 hacluster /tmp1,/tmp2,/tmp3
 # hdfs dfsrouteradmin -update /apps1 hacluster /tmp1,/tmp2,/tmp3 -order RANDOM

*Actual*. With the above commands, mount entry is successfully updated.

But order information like HASH, RANDOM is not displayed in mount entries and 
also not displayed in federation router UI. However order information is 
updated properly when there are multiple nameservices. This issue is with 
single nameservice having multiple destinations.

*Expected:* 

*Order information should be updated in mount entries so that the user will 
come to know which order has been set.*

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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



[jira] [Created] (HDFS-13842) RBF : Exceptions are conflicting If we try to create the same mount entry once again

2018-08-21 Thread Soumyapn (JIRA)
Soumyapn created HDFS-13842:
---

 Summary: RBF : Exceptions are conflicting If we try to create the 
same mount entry once again
 Key: HDFS-13842
 URL: https://issues.apache.org/jira/browse/HDFS-13842
 Project: Hadoop HDFS
  Issue Type: Bug
Reporter: Soumyapn


Test Steps:
 # Execute the command : hdfs dfsrouteradmin -add /apps7 hacluster /tmp7
 # Execute the same command once again.

Expected Result:

User should get the message saying already the mount entry is present.

 

Actual Result:

console message is displayed like below.

"Cannot add destination at hacluster /tmp7
Successfully added mount point /apps7"

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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



[jira] [Resolved] (HDFS-3584) Blocks are getting marked as corrupt with append operation under high load.

2018-08-21 Thread Wei-Chiu Chuang (JIRA)


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

Wei-Chiu Chuang resolved HDFS-3584.
---
  Resolution: Duplicate
Target Version/s:   (was: )

Close this one. Thanks for reminder [~elgoiri]

> Blocks are getting marked as corrupt with append operation under high load.
> ---
>
> Key: HDFS-3584
> URL: https://issues.apache.org/jira/browse/HDFS-3584
> Project: Hadoop HDFS
>  Issue Type: Bug
>  Components: namenode
>Affects Versions: 2.0.0-alpha
>Reporter: Brahma Reddy Battula
>Priority: Major
>
> Scenario:
> = 
> 1. There are 2 clients cli1 and cli2 cli1 write a file F1 and not closed
> 2. The cli2 will call append on unclosed file and triggers a leaserecovery
> 3. Cli1 is closed
> 4. Lease recovery is completed and with updated GS in DN and got BlockReport 
> since there is a mismatch in GS the block got corrupted
> 5. Now we got a CommitBlockSync this will also fail since the File is already 
> closed by cli1 and state in NN is Finalized



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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



[jira] [Created] (HDFS-13841) RBF : After Click on another Tab in RouterFederation UI page it's not redirecting to new tab

2018-08-21 Thread Harshakiran Reddy (JIRA)
Harshakiran Reddy created HDFS-13841:


 Summary: RBF : After Click on another Tab in RouterFederation UI 
page it's not redirecting to new tab 
 Key: HDFS-13841
 URL: https://issues.apache.org/jira/browse/HDFS-13841
 Project: Hadoop HDFS
  Issue Type: Bug
  Components: federation
Affects Versions: 3.1.0
Reporter: Harshakiran Reddy


{{Scenario :-}}

1. Open the Federation UI
2. Click on Different tabs like {{Mount Tables}} , {{Router}} or {{Subcluster}}
3. when we click on mount table tab or any other tab it will redirect to that 
page but it's not happening when we do refresh the page or submit the Enter 
button that time it's redirected to particular clicked Tab page.

{{Expected Result :-}}

It should redirect to clicked Tab page.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
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: trunk+JDK8 on Windows/x64

2018-08-21 Thread Apache Jenkins Server
For more details, see https://builds.apache.org/job/hadoop-trunk-win/565/

[Aug 20, 2018 3:01:59 PM] (yqlin) HDFS-13750. RBF: Router ID in RouterRpcClient 
is always null.
[Aug 20, 2018 3:14:40 PM] (jlowe) YARN-8242. YARN NM: OOM error while reading 
back the state store on
[Aug 20, 2018 7:22:36 PM] (gifuma) YARN-8673. [AMRMProxy] More robust 
responseId resync after an YarnRM
[Aug 20, 2018 9:33:16 PM] (gifuma) YARN-8581. [AMRMProxy] Add sub-cluster 
timeout in
[Aug 21, 2018 1:36:24 AM] (stevel) HADOOP-15679. ShutdownHookManager shutdown 
time needs to be configurable
[Aug 21, 2018 4:03:19 AM] (vinayakumarb) HDFS-13772. Erasure coding: 
Unnecessary NameNode Logs displaying for
[Aug 21, 2018 6:28:07 AM] (rohithsharmaks) YARN-8129. Improve error message for 
invalid value in fields attribute.
[Aug 21, 2018 11:00:31 AM] (wwei) YARN-8683. Support to display pending 
scheduling requests in RM app


ERROR: File 'out/email-report.txt' does not exist

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

[jira] [Created] (HDFS-13840) RBW Blocks which are having less GS shouldn't added on DN restart

2018-08-21 Thread Brahma Reddy Battula (JIRA)
Brahma Reddy Battula created HDFS-13840:
---

 Summary: RBW Blocks which are having less GS shouldn't added on DN 
restart
 Key: HDFS-13840
 URL: https://issues.apache.org/jira/browse/HDFS-13840
 Project: Hadoop HDFS
  Issue Type: Bug
Reporter: Brahma Reddy Battula
Assignee: Brahma Reddy Battula


# Start two DN's  (DN1,DN2).
 # Write fileA with rep=2 ( dn't close)
 # Stop DN1.
 # Write some data to fileA.
 # restart the DN1
 # Get the blocklocations of fileA.

Here RWR state block will be reported on DN restart and added to locations.

IMO,RWR blocks which having less GS shouldn't added, as they give false postive 
(anyway read can be failed as it's genstamp is less)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
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: trunk+JDK8 on Linux/x86

2018-08-21 Thread Apache Jenkins Server
For more details, see 
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/875/

[Aug 20, 2018 6:50:29 AM] (brahma) HDFS-13790. RBF: Move ClientProtocol APIs to 
its own module. Contributed
[Aug 20, 2018 8:07:58 AM] (msingh) HDDS-353. Multiple delete Blocks tests are 
failing consistently.
[Aug 20, 2018 3:01:59 PM] (yqlin) HDFS-13750. RBF: Router ID in RouterRpcClient 
is always null.
[Aug 20, 2018 3:14:40 PM] (jlowe) YARN-8242. YARN NM: OOM error while reading 
back the state store on
[Aug 20, 2018 7:22:36 PM] (gifuma) YARN-8673. [AMRMProxy] More robust 
responseId resync after an YarnRM
[Aug 20, 2018 9:33:16 PM] (gifuma) YARN-8581. [AMRMProxy] Add sub-cluster 
timeout in


[Error replacing 'FILE' - Workspace is not accessible]

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

[jira] [Resolved] (HDDS-367) Cleanup GettingStarted page to remove usage of ksm

2018-08-21 Thread Dinesh Chitlangia (JIRA)


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

Dinesh Chitlangia resolved HDDS-367.

Resolution: Invalid

> Cleanup GettingStarted page to remove usage of ksm
> --
>
> Key: HDDS-367
> URL: https://issues.apache.org/jira/browse/HDDS-367
> Project: Hadoop Distributed Data Store
>  Issue Type: Bug
>  Components: document
>Reporter: Dinesh Chitlangia
>Assignee: Dinesh Chitlangia
>Priority: Trivial
>
> As part of HDDS-167, KeySpaceManager was renamed to OzoneManager and thus 
> usage of ksm was replaced with om.
> There are still some traces of ksm in Getting Started page where the commands 
> and configuration properties use ksm instead of om.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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



[jira] [Created] (HDDS-367) Cleanup GettingStarted page to remove usage of ksm

2018-08-21 Thread Dinesh Chitlangia (JIRA)
Dinesh Chitlangia created HDDS-367:
--

 Summary: Cleanup GettingStarted page to remove usage of ksm
 Key: HDDS-367
 URL: https://issues.apache.org/jira/browse/HDDS-367
 Project: Hadoop Distributed Data Store
  Issue Type: Bug
  Components: document
 Environment: As part of HDDS-167, KeySpaceManager was renamed to 
OzoneManager and thus usage of ksm was replaced with om.

There are still some traces of ksm in Getting Started page where the commands 
and configuration properties use ksm instead of om.

 
Reporter: Dinesh Chitlangia
Assignee: Dinesh Chitlangia






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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



[jira] [Created] (HDFS-13839) Add order information in dfsrouteradmin "-ls" command

2018-08-21 Thread Soumyapn (JIRA)
Soumyapn created HDFS-13839:
---

 Summary: Add order information in dfsrouteradmin "-ls" command
 Key: HDFS-13839
 URL: https://issues.apache.org/jira/browse/HDFS-13839
 Project: Hadoop HDFS
  Issue Type: Bug
  Components: federation
Reporter: Soumyapn


Scenario:

If we execute the hdfs dfsrouteradmin -ls  command, order information is 
not present.

Example:

./hdfs dfsrouteradmin -ls /apps1

With the above command: Source, Destinations, Owner, Group, Mode,Quota/Usage 
information is displayed. But there is no "order" information displayed with 
the "ls" command

 

Expected:

order information should be displayed with the -ls command to know the order 
set.

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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