[ https://issues.apache.org/jira/browse/GEODE-5884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16669600#comment-16669600 ]
ASF subversion and git services commented on GEODE-5884: -------------------------------------------------------- Commit 913cec14fd9918918a8f0ada451344fd990e7586 in geode's branch refs/heads/develop from [~huynhja] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=913cec1 ] GEODE-5884: Non HA Function waits for all results if exception occurs * Non HA functions will attempt to return as many results as possible when an exception occurs * This behavior will be more in-line with single-hop execution > Executing a function with non HA should return any available partial results > ---------------------------------------------------------------------------- > > Key: GEODE-5884 > URL: https://issues.apache.org/jira/browse/GEODE-5884 > Project: Geode > Issue Type: Bug > Components: functions > Affects Versions: 1.0.0-incubating > Reporter: Jason Huynh > Assignee: Jason Huynh > Priority: Major > Labels: pull-request-available > Time Spent: 40m > Remaining Estimate: 0h > > When a function is executed without single hop, it is sent to a > "coordinating" node. This node then creates tasks that are executed on other > remote nodes and itself. If any of the remote nodes or the local node gets > an exception, it will accumulate the exception and any results it has > currently received. It then completes and sends those results back to the > client. > There is a flag to waitOnException. We should set this to true if the > function is non HA. This will have the coordinating node wait for all > results before sending back to the client. The work is going to get executed > on the remote nodes anyways, so why not wait for the results? > This will mirror a single-hop execution where a single node may fail. If it > does, the client still receives results from the other nodes. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)