[ https://issues.apache.org/jira/browse/YARN-5269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15903540#comment-15903540 ]
Haibo Chen edited comment on YARN-5269 at 3/9/17 10:08 PM: ----------------------------------------------------------- Based on today's discussion, questions we need to answer are 1) for the synchronous putEntities() API, what do we promise if no error/exception is returned to clients? In what scenarios do we bubble exceptions/errors to clients? 2) similarly for the asynchronous write API This is more to explicate the semantics+guarantees of our write API so that clients will have correct expectations. I'll check the existing code base and share my findings. [~vrushalic], [~jrottinghuis] can chime in on more complicated scenarios where spooled-buffered-mutator is involved. was (Author: haibochen): Based on today's discussion, questions we need to answer are 1) for the synchronous putEntities() API, what do we promise if no error/exception is returned to clients? In what scenarios do we bubble exceptions/errors to clients? 2) similarly for the asynchronous write API This is more to explicate the semantics+guarantees of our write API so that clients will have correct expectations. I'll check the existing code base and share my findings. [~vrushalic], [~jrottinghuis] chime in on more complicated scenarios where spooled-buffered-mutator is involved. > Bubble exceptions and errors all the way up the calls, including to clients. > ---------------------------------------------------------------------------- > > Key: YARN-5269 > URL: https://issues.apache.org/jira/browse/YARN-5269 > Project: Hadoop YARN > Issue Type: Sub-task > Components: timelineserver > Affects Versions: YARN-2928 > Reporter: Joep Rottinghuis > Assignee: Haibo Chen > Labels: YARN-5355, yarn-5355-merge-blocker > > Currently we ignore (swallow) exception from the HBase side in many cases > (reads and writes). > Also, on the client side, neither TimelineClient#putEntities (the v2 flavor) > nor the #putEntitiesAsync method return any value. > For the second drop we may want to consider how we properly bubble up > exceptions throughout the write and reader call paths and if we want to > return a response in putEntities and some future kind of result for > putEntitiesAsync. -- This message was sent by Atlassian JIRA (v6.3.15#6346) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org