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 2019/07/04 06:53:00 UTC
[jira] [Work logged] (HDDS-1729) Ozone Client should timeout if the
put block futures are taking a long time
[ https://issues.apache.org/jira/browse/HDDS-1729?focusedWorklogId=272015&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-272015 ]
ASF GitHub Bot logged work on HDDS-1729:
----------------------------------------
Author: ASF GitHub Bot
Created on: 04/Jul/19 06:52
Start Date: 04/Jul/19 06:52
Worklog Time Spent: 10m
Work Description: bshashikant commented on issue #1024: HDDS-1729. Ozone Client should timeout if the put block futures are taking a long time. Contributed by Mukul Kumar Singh.
URL: https://github.com/apache/hadoop/pull/1024#issuecomment-508362549
Thanks @mukul1987 .
Every putBlock future will eventually complete once the retry policy set in RaftClient expires. I don't think we need extra timeout set in ozone client for putBlock. What do you think ?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 272015)
Time Spent: 0.5h (was: 20m)
> Ozone Client should timeout if the put block futures are taking a long time
> ---------------------------------------------------------------------------
>
> Key: HDDS-1729
> URL: https://issues.apache.org/jira/browse/HDDS-1729
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Components: Ozone Client
> Affects Versions: 0.4.0
> Reporter: Mukul Kumar Singh
> Assignee: Mukul Kumar Singh
> Priority: Major
> Labels: pull-request-available
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Ozone client currently enqueues a put future to the future map, However if the pipeline is slow, the client does not timeout and wait for the future to finish. For reasonable latency in the system, the client should timeout
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org