[
https://issues.apache.org/jira/browse/HADOOP-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12474264
]
Tom White commented on HADOOP-601:
----------------------------------
Thanks Johan. It would be good to add the annotations handling from your patch
to the mechanism in HADOOP-997. This is probably best done after HADOOP-997 is
committed, as one of a series of follow up Jiras to introduce retries in
various parts of Hadoop. Note that if you use annotations you can't get
parameters from the configuration file (unless anyone knows of a way to do
this?)
Also, I've put the retry classes in a new package org.apache.hadoop.io.retry.
Do people feel this is OK? It doesn't feel quite right as it's not exclusively
for IO retries.
> we need some rpc retry framework
> --------------------------------
>
> Key: HADOOP-601
> URL: https://issues.apache.org/jira/browse/HADOOP-601
> Project: Hadoop
> Issue Type: Improvement
> Components: ipc
> Affects Versions: 0.11.2
> Reporter: Owen O'Malley
> Assigned To: Owen O'Malley
> Attachments: HADOOP-601-v1.patch, HADOOP-601-v1.patch
>
>
> We need some mechanism for RPC calls that get exceptions to automatically
> retry the call under certain circumstances. In particular, we often end up
> with calls to rpcs being wrapped with retry loops for timeouts. We should be
> able to make a retrying proxy that will call the rpc and retry in some
> circumstances.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
