> On Jan. 23, 2019, 3:33 p.m., James DeFelice wrote:
> > src/resource_provider/storage/provider.cpp
> > Lines 1916 (patched)
> > <https://reviews.apache.org/r/69812/diff/1/?file=2121403#file2121403line1916>
> >
> >     what about a metric for call retries?
> 
> Chun-Hung Hsiao wrote:
>     `resource_providers/<type>.<name>/csi_plugin/rpcs/<rpc>/errors` should be 
> a good approximation. I'll create a follow-up patch for finer-grained error 
> metrics, but probably won't backport it. Is it good enough?

Yes, good enough. Thanks.


- James


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/69812/#review212242
-----------------------------------------------------------


On Jan. 23, 2019, 7:10 a.m., Chun-Hung Hsiao wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/69812/
> -----------------------------------------------------------
> 
> (Updated Jan. 23, 2019, 7:10 a.m.)
> 
> 
> Review request for mesos, Benjamin Bannier, James DeFelice, Jie Yu, and Jan 
> Schlicht.
> 
> 
> Bugs: MESOS-9517
>     https://issues.apache.org/jira/browse/MESOS-9517
> 
> 
> Repository: mesos
> 
> 
> Description
> -------
> 
> When the CSI plugin returns a retryable error (i.e., `DEADLINE_EXCEEDED`
> or `UNAVAILABLE`) for `CreateVolume` or `DeleteVolume` CSI calls, SLRP
> will now retry indefinitely with a random exponential backoff.
> 
> 
> Diffs
> -----
> 
>   src/csi/client.hpp 5d40d54c2abbd03993ce8835d37db23e209c7554 
>   src/csi/client.cpp 61ed410985099828a2f58b1527ab57daa4b379df 
>   src/resource_provider/storage/provider.hpp 
> 331f7b785b14b814c2889488effd53f3a48a1b95 
>   src/resource_provider/storage/provider.cpp 
> d6e20a549ede189c757ae3ae922ab7cb86d2be2c 
> 
> 
> Diff: https://reviews.apache.org/r/69812/diff/2/
> 
> 
> Testing
> -------
> 
> make check
> 
> A unit test will be added later in the chain.
> 
> 
> Thanks,
> 
> Chun-Hung Hsiao
> 
>

Reply via email to