[jira] [Updated] (HDFS-15108) RBF: MembershipNamenodeResolver should invalidate cache incase of active namenode update

2020-01-10 Thread Ayush Saxena (Jira) 


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

Ayush Saxena updated HDFS-15108:

Fix Version/s: 3.3.0
 Hadoop Flags: Reviewed
   Resolution: Fixed
   Status: Resolved  (was: Patch Available)

> RBF: MembershipNamenodeResolver should invalidate cache incase of active 
> namenode update
> 
>
> Key: HDFS-15108
> URL: https://issues.apache.org/jira/browse/HDFS-15108
> Project: Hadoop HDFS
>  Issue Type: Bug
>Reporter: Ayush Saxena
>Assignee: Ayush Saxena
>Priority: Major
> Fix For: 3.3.0
>
> Attachments: HDFS-15108-01.patch, HDFS-15108-02.patch, 
> HDFS-15108-03.patch, HDFS-15108-04.patch, HDFS-15108-05.patch
>
>
> If a failover happens, {{namenodeResolver.updateActiveNamenode(nsId, 
> address);}} is called, but this doesn't invalidates the cache, so as the next 
> time the correct active is fetched.



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

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

[jira] [Updated] (HDFS-15108) RBF: MembershipNamenodeResolver should invalidate cache incase of active namenode update

2020-01-10 Thread Ayush Saxena (Jira) 


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

Ayush Saxena updated HDFS-15108:

Attachment: HDFS-15108-05.patch

> RBF: MembershipNamenodeResolver should invalidate cache incase of active 
> namenode update
> 
>
> Key: HDFS-15108
> URL: https://issues.apache.org/jira/browse/HDFS-15108
> Project: Hadoop HDFS
>  Issue Type: Bug
>Reporter: Ayush Saxena
>Assignee: Ayush Saxena
>Priority: Major
> Attachments: HDFS-15108-01.patch, HDFS-15108-02.patch, 
> HDFS-15108-03.patch, HDFS-15108-04.patch, HDFS-15108-05.patch
>
>
> If a failover happens, {{namenodeResolver.updateActiveNamenode(nsId, 
> address);}} is called, but this doesn't invalidates the cache, so as the next 
> time the correct active is fetched.



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

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

[jira] [Updated] (HDFS-15108) RBF: MembershipNamenodeResolver should invalidate cache incase of active namenode update

2020-01-10 Thread Ayush Saxena (Jira) 


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

Ayush Saxena updated HDFS-15108:

Attachment: HDFS-15108-04.patch

> RBF: MembershipNamenodeResolver should invalidate cache incase of active 
> namenode update
> 
>
> Key: HDFS-15108
> URL: https://issues.apache.org/jira/browse/HDFS-15108
> Project: Hadoop HDFS
>  Issue Type: Bug
>Reporter: Ayush Saxena
>Assignee: Ayush Saxena
>Priority: Major
> Attachments: HDFS-15108-01.patch, HDFS-15108-02.patch, 
> HDFS-15108-03.patch, HDFS-15108-04.patch
>
>
> If a failover happens, {{namenodeResolver.updateActiveNamenode(nsId, 
> address);}} is called, but this doesn't invalidates the cache, so as the next 
> time the correct active is fetched.



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

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

[jira] [Updated] (HDFS-15108) RBF: MembershipNamenodeResolver should invalidate cache incase of active namenode update

2020-01-10 Thread Ayush Saxena (Jira) 


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

Ayush Saxena updated HDFS-15108:

Attachment: HDFS-15108-03.patch

> RBF: MembershipNamenodeResolver should invalidate cache incase of active 
> namenode update
> 
>
> Key: HDFS-15108
> URL: https://issues.apache.org/jira/browse/HDFS-15108
> Project: Hadoop HDFS
>  Issue Type: Bug
>Reporter: Ayush Saxena
>Assignee: Ayush Saxena
>Priority: Major
> Attachments: HDFS-15108-01.patch, HDFS-15108-02.patch, 
> HDFS-15108-03.patch
>
>
> If a failover happens, {{namenodeResolver.updateActiveNamenode(nsId, 
> address);}} is called, but this doesn't invalidates the cache, so as the next 
> time the correct active is fetched.



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

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

[jira] [Updated] (HDFS-15108) RBF: MembershipNamenodeResolver should invalidate cache incase of active namenode update

2020-01-09 Thread Ayush Saxena (Jira) 


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

Ayush Saxena updated HDFS-15108:

Attachment: HDFS-15108-02.patch

> RBF: MembershipNamenodeResolver should invalidate cache incase of active 
> namenode update
> 
>
> Key: HDFS-15108
> URL: https://issues.apache.org/jira/browse/HDFS-15108
> Project: Hadoop HDFS
>  Issue Type: Bug
>Reporter: Ayush Saxena
>Assignee: Ayush Saxena
>Priority: Major
> Attachments: HDFS-15108-01.patch, HDFS-15108-02.patch
>
>
> If a failover happens, {{namenodeResolver.updateActiveNamenode(nsId, 
> address);}} is called, but this doesn't invalidates the cache, so as the next 
> time the correct active is fetched.



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

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

[jira] [Updated] (HDFS-15108) RBF: MembershipNamenodeResolver should invalidate cache incase of active namenode update

2020-01-09 Thread Ayush Saxena (Jira) 


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

Ayush Saxena updated HDFS-15108:

Attachment: HDFS-15108-02.patch

> RBF: MembershipNamenodeResolver should invalidate cache incase of active 
> namenode update
> 
>
> Key: HDFS-15108
> URL: https://issues.apache.org/jira/browse/HDFS-15108
> Project: Hadoop HDFS
>  Issue Type: Bug
>Reporter: Ayush Saxena
>Assignee: Ayush Saxena
>Priority: Major
> Attachments: HDFS-15108-01.patch
>
>
> If a failover happens, {{namenodeResolver.updateActiveNamenode(nsId, 
> address);}} is called, but this doesn't invalidates the cache, so as the next 
> time the correct active is fetched.



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

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

[jira] [Updated] (HDFS-15108) RBF: MembershipNamenodeResolver should invalidate cache incase of active namenode update

2020-01-09 Thread Ayush Saxena (Jira) 


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

Ayush Saxena updated HDFS-15108:

Attachment: (was: HDFS-15108-02.patch)

> RBF: MembershipNamenodeResolver should invalidate cache incase of active 
> namenode update
> 
>
> Key: HDFS-15108
> URL: https://issues.apache.org/jira/browse/HDFS-15108
> Project: Hadoop HDFS
>  Issue Type: Bug
>Reporter: Ayush Saxena
>Assignee: Ayush Saxena
>Priority: Major
> Attachments: HDFS-15108-01.patch
>
>
> If a failover happens, {{namenodeResolver.updateActiveNamenode(nsId, 
> address);}} is called, but this doesn't invalidates the cache, so as the next 
> time the correct active is fetched.



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

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

[jira] [Updated] (HDFS-15108) RBF: MembershipNamenodeResolver should invalidate cache incase of active namenode update

2020-01-09 Thread Ayush Saxena (Jira) 


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

Ayush Saxena updated HDFS-15108:

Status: Patch Available  (was: Open)

> RBF: MembershipNamenodeResolver should invalidate cache incase of active 
> namenode update
> 
>
> Key: HDFS-15108
> URL: https://issues.apache.org/jira/browse/HDFS-15108
> Project: Hadoop HDFS
>  Issue Type: Bug
>Reporter: Ayush Saxena
>Assignee: Ayush Saxena
>Priority: Major
> Attachments: HDFS-15108-01.patch
>
>
> If a failover happens, {{namenodeResolver.updateActiveNamenode(nsId, 
> address);}} is called, but this doesn't invalidates the cache, so as the next 
> time the correct active is fetched.



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

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

[jira] [Updated] (HDFS-15108) RBF: MembershipNamenodeResolver should invalidate cache incase of active namenode update

2020-01-09 Thread Ayush Saxena (Jira) 


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

Ayush Saxena updated HDFS-15108:

Attachment: HDFS-15108-01.patch

> RBF: MembershipNamenodeResolver should invalidate cache incase of active 
> namenode update
> 
>
> Key: HDFS-15108
> URL: https://issues.apache.org/jira/browse/HDFS-15108
> Project: Hadoop HDFS
>  Issue Type: Bug
>Reporter: Ayush Saxena
>Assignee: Ayush Saxena
>Priority: Major
> Attachments: HDFS-15108-01.patch
>
>
> If a failover happens, {{namenodeResolver.updateActiveNamenode(nsId, 
> address);}} is called, but this doesn't invalidates the cache, so as the next 
> time the correct active is fetched.



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

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