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

Uma Maheswara Rao G updated HADOOP-17024:
-----------------------------------------
    Description: 
As part of the design doc HDFS-15289, [~sanjay.radia] and discussed the 
following scenarios when fallback enabled.

*Behavior when fallback enabled:*

       Assume FS trees and mount mappings like below:

           mount link /a/b/c/d  → hdfs://nn1/a/b

           mount link /a/p/q/r  → hdfs://nn2/a/b    

           fallback → hdfs://nn3/  $  /a/c
                                                 /x/z
 # Open(/x/y) then it goes to nn3 (fallback)      - WORKS
 # Create(/x/foo) then foo is created in nn3 in dir /x   - WORKS
 # ls /  should list   /a  /x .Today this does not work and IT IS A BUG!!! 
Because it conflicts with the open(/x/y)
 # Create /y  : fails  - also fails when not using  fallback  - WORKS
 # Create /a/z : fails - also fails when not using  fallback - WORKS
 # ls /a should list /b /p  as expected and will not show fallback in nn3 - 
WORKS

 

This Jira will fix issue of #3. So, when fallback enabled it should show merged 
ls view with mount links + fallback root. ( this will only be at root level)

  was:
As part of the design doc, [~sanjay.radia] and discussed the following 
scenarios when fallback enabled.

 *Behavior when fallback enabled:*

       Assume FS trees and mount mappings like below:

           mount link /a/b/c/d  → hdfs://nn1/a/b

           mount link /a/p/q/r  → hdfs://nn2/a/b    

           fallback → hdfs://nn3/  $  /a/c
                                                 /x/z
 # Open(/x/y) then it goes to nn3 (fallback)      - WORKS
 # Create(/x/foo) then foo is created in nn3 in dir /x   - WORKS
 # ls /  should list   /a  /x .Today this does not work and IT IS A BUG!!! 
Because it conflicts with the open(/x/y)
 # Create /y  : fails  - also fails when not using  fallback  - WORKS
 # Create /a/z : fails - also fails when not using  fallback - WORKS
 # ls /a should list /b /p  as expected and will not show fallback in nn3 - 
WORKS

 

This Jira will fix issue of #3. So, when fallback enabled it should show merged 
ls view with mount links + fallback root. ( this will only be at root level)


> ListStatus on ViewFS root (ls "/") should list the linkFallBack root 
> (configured target root).
> ----------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-17024
>                 URL: https://issues.apache.org/jira/browse/HADOOP-17024
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: fs, viewfs
>    Affects Versions: 3.2.2
>            Reporter: Uma Maheswara Rao G
>            Priority: Major
>
> As part of the design doc HDFS-15289, [~sanjay.radia] and discussed the 
> following scenarios when fallback enabled.
> *Behavior when fallback enabled:*
>        Assume FS trees and mount mappings like below:
>            mount link /a/b/c/d  → hdfs://nn1/a/b
>            mount link /a/p/q/r  → hdfs://nn2/a/b    
>            fallback → hdfs://nn3/  $  /a/c
>                                                  /x/z
>  # Open(/x/y) then it goes to nn3 (fallback)      - WORKS
>  # Create(/x/foo) then foo is created in nn3 in dir /x   - WORKS
>  # ls /  should list   /a  /x .Today this does not work and IT IS A BUG!!! 
> Because it conflicts with the open(/x/y)
>  # Create /y  : fails  - also fails when not using  fallback  - WORKS
>  # Create /a/z : fails - also fails when not using  fallback - WORKS
>  # ls /a should list /b /p  as expected and will not show fallback in nn3 - 
> WORKS
>  
> This Jira will fix issue of #3. So, when fallback enabled it should show 
> merged ls view with mount links + fallback root. ( this will only be at root 
> level)



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to