[
https://issues.apache.org/jira/browse/LENS-743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15048519#comment-15048519
]
Puneet Gupta commented on LENS-743:
-----------------------------------
Some more thoughts ..
1. We need a way to tell how many times a query was retried . Are we planning
to add Retry Count to DB also ?
2. What about other details in DB like
> status = should it show RETRYING
> errormessage = Latest error msg or appended error messages . How should we
> (if at all) show error messages from previous runs ? If the query succeeds
> finally will we wipe this field empty ?
> driver Start and driver End Time : start time of first try and end time of
> the last try ? or all for the last try .
> If for some reason (say driver load sharing), a different driver is picked,
> what happens to driverClass (now called driverName)?
3. Query Logs.
can we put up pros and cons of both the approaches (using new handle vs reusing
same handle).
> Query failure retries for transient errors
> ------------------------------------------
>
> Key: LENS-743
> URL: https://issues.apache.org/jira/browse/LENS-743
> Project: Apache Lens
> Issue Type: Improvement
> Components: server
> Reporter: Amareshwari Sriramadasu
> Assignee: Rajat Khandelwal
> Labels: newbie
>
> There have to be retries for query failures for transient errors like network
> errors (Hive server not reachable/ Metastore not reachable/ DB not
> reachable). Retries should be available for each phase - submission,
> execution, updating status, fetching results and formatting.
> Right now, any such failure results in marking query as failed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
