[
https://issues.apache.org/jira/browse/HDFS-11146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16111229#comment-16111229
]
Daryn Sharp commented on HDFS-11146:
------------------------------------
Yes, this appears it would destroy the NN with FBRs. I'd rather see the
existing DNA_REGISTER command, rather than a new command, be used to indirectly
solicit a FBR. The register will schedule the FBR request a short time in the
future and utilize the existing FBR leases to avoid the storm.
I'd rather not have the common case for heartbeat processing taking the extra
expense for a rare use case of failover. It would be better for the heartbeat
monitor to introduce the expense on a less frequent basis. It can call
setForceRegistration on the datanode descriptor and the next heartbeat will
trigger a FBR.
> Excess replicas will not be deleted until all storages's FBR received after
> failover
> ------------------------------------------------------------------------------------
>
> Key: HDFS-11146
> URL: https://issues.apache.org/jira/browse/HDFS-11146
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Brahma Reddy Battula
> Assignee: Brahma Reddy Battula
> Attachments: HDFS-11146-002.patch, HDFS-11146-003.patch,
> HDFS-11146.patch
>
>
> Excess replicas will not be deleted until all storages's FBR received after
> failover.
> Thinking following soultion can help.
> *Solution:*
> I think after failover, As DNs aware of failover ,so they can send another
> block report (FBR) irrespective of interval.May be some shuffle can be done,
> similar to initial delay.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
