You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/07/31 03:47:00 UTC
[jira] [Work logged] (HDFS-16699) RBF: Router Update Observer NameNode state to Active when failover because of sockeTimeOut Exception
[ https://issues.apache.org/jira/browse/HDFS-16699?focusedWorklogId=796676&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-796676 ]
ASF GitHub Bot logged work on HDFS-16699:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 31/Jul/22 03:46
Start Date: 31/Jul/22 03:46
Worklog Time Spent: 10m
Work Description: SanQiMax opened a new pull request, #4663:
URL: https://github.com/apache/hadoop/pull/4663
…ver because of sockeTimeOut Exception
<!--
Thanks for sending a pull request!
1. If this is your first time, please read our contributor guidelines: https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute
2. Make sure your PR title starts with JIRA issue id, e.g., 'HADOOP-17799. Your PR title ...'.
-->
### Description of PR
### How was this patch tested?
### For code changes:
- [ ] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
- [ ] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
- [ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`, `NOTICE-binary` files?
Issue Time Tracking
-------------------
Worklog Id: (was: 796676)
Remaining Estimate: 0h
Time Spent: 10m
> RBF: Router Update Observer NameNode state to Active when failover because of sockeTimeOut Exception
> ------------------------------------------------------------------------------------------------------
>
> Key: HDFS-16699
> URL: https://issues.apache.org/jira/browse/HDFS-16699
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: rbf
> Affects Versions: 3.1.1
> Reporter: ShuangQi Xia
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> we found that ,router print logs that indicate Observer NameNode state changed to active always,here's the log
> 2022-03-18 11:00:54,589 | INFO | NamenodeHeartbeatService hacluster 11342-0 | NN registration state has changed: test101:25019->hacluster:11342:test103:25000-ACTIVE -> test102:25019->hacluster:11342::test103:25000-OBSERVER | MembershipStoreImpl.java:170
> for code ,I fount that , when router request failed for some reson ,like sockettimeout Excetion , failover to Observer NameNode，will update it's state to Active
> if (failover) {
> // Success on alternate server, update
> InetSocketAddress address = client.getAddress();
> namenodeResolver.updateActiveNamenode(nsId, address);
> }
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org