[
https://issues.apache.org/jira/browse/YARN-5269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joep Rottinghuis updated YARN-5269:
-----------------------------------
Comment: was deleted
(was: YARN-5269-YARN-2928.01.patch: Untested initial outline of what I think
might work.
Need to do manual testing and come up with a good way to create a unit test for
this.
I'm still considering if we want to use the same approach in the Coprocessor.
It would probably not be needed, as the only cluster where those are deployed
will be on the HBase cluster hosting the timeline service tables.
I might still add it so that folks can choose to have separate config variables
(timeouts etc) for the timeline coprocessors than for other ones.
This also reminds me that we should update the documentation to clarify that
the
yarn.timeline-service.hbase.coprocessor.app-final-value-retention-milliseconds
value needs to be present in the config on the region server.
)
> 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
>
> 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.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
