[jira] [Updated] (TEZ-2259) Push additional data to Timeline for Recovery for better consumption in UI
[ https://issues.apache.org/jira/browse/TEZ-2259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah updated TEZ-2259: - Attachment: TEZ-2259.branch-06.patch branch 0.6 patch as master patch conflicts. Push additional data to Timeline for Recovery for better consumption in UI -- Key: TEZ-2259 URL: https://issues.apache.org/jira/browse/TEZ-2259 Project: Apache Tez Issue Type: Bug Reporter: Hitesh Shah Assignee: Hitesh Shah Attachments: TEZ-2259.1.patch, TEZ-2259.2.patch, TEZ-2259.3.patch, TEZ-2259.4.patch, TEZ-2259.branch-06.patch Some things I can think of: - applicationAttemptId in which the dag was submitted - appAttemptId in which the dag was completed Above provides implicit information on how many app attempts the dag spanned ( and therefore recovered how many times ). - Maybe an implicit event mentioning that the DAG was recovered and in which attempt it was recovered. Possibly add information on what state was recovered? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TEZ-2259) Push additional data to Timeline for Recovery for better consumption in UI
[ https://issues.apache.org/jira/browse/TEZ-2259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah updated TEZ-2259: - Attachment: TEZ-2259.4.patch Re-based stale patch Push additional data to Timeline for Recovery for better consumption in UI -- Key: TEZ-2259 URL: https://issues.apache.org/jira/browse/TEZ-2259 Project: Apache Tez Issue Type: Bug Reporter: Hitesh Shah Assignee: Hitesh Shah Attachments: TEZ-2259.1.patch, TEZ-2259.2.patch, TEZ-2259.3.patch, TEZ-2259.4.patch Some things I can think of: - applicationAttemptId in which the dag was submitted - appAttemptId in which the dag was completed Above provides implicit information on how many app attempts the dag spanned ( and therefore recovered how many times ). - Maybe an implicit event mentioning that the DAG was recovered and in which attempt it was recovered. Possibly add information on what state was recovered? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TEZ-2259) Push additional data to Timeline for Recovery for better consumption in UI
[ https://issues.apache.org/jira/browse/TEZ-2259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah updated TEZ-2259: - Attachment: TEZ-2259.2.patch Push additional data to Timeline for Recovery for better consumption in UI -- Key: TEZ-2259 URL: https://issues.apache.org/jira/browse/TEZ-2259 Project: Apache Tez Issue Type: Bug Reporter: Hitesh Shah Assignee: Hitesh Shah Attachments: TEZ-2259.1.patch, TEZ-2259.2.patch Some things I can think of: - applicationAttemptId in which the dag was submitted - appAttemptId in which the dag was completed Above provides implicit information on how many app attempts the dag spanned ( and therefore recovered how many times ). - Maybe an implicit event mentioning that the DAG was recovered and in which attempt it was recovered. Possibly add information on what state was recovered? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TEZ-2259) Push additional data to Timeline for Recovery for better consumption in UI
[ https://issues.apache.org/jira/browse/TEZ-2259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah updated TEZ-2259: - Attachment: TEZ-2259.3.patch Comments addressed. Push additional data to Timeline for Recovery for better consumption in UI -- Key: TEZ-2259 URL: https://issues.apache.org/jira/browse/TEZ-2259 Project: Apache Tez Issue Type: Bug Reporter: Hitesh Shah Assignee: Hitesh Shah Attachments: TEZ-2259.1.patch, TEZ-2259.2.patch, TEZ-2259.3.patch Some things I can think of: - applicationAttemptId in which the dag was submitted - appAttemptId in which the dag was completed Above provides implicit information on how many app attempts the dag spanned ( and therefore recovered how many times ). - Maybe an implicit event mentioning that the DAG was recovered and in which attempt it was recovered. Possibly add information on what state was recovered? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TEZ-2259) Push additional data to Timeline for Recovery for better consumption in UI
[ https://issues.apache.org/jira/browse/TEZ-2259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah updated TEZ-2259: - Attachment: TEZ-2259.1.patch [~zjffdu] [~pramachandran] review please. Push additional data to Timeline for Recovery for better consumption in UI -- Key: TEZ-2259 URL: https://issues.apache.org/jira/browse/TEZ-2259 Project: Apache Tez Issue Type: Bug Reporter: Hitesh Shah Assignee: Hitesh Shah Attachments: TEZ-2259.1.patch Some things I can think of: - applicationAttemptId in which the dag was submitted - appAttemptId in which the dag was completed Above provides implicit information on how many app attempts the dag spanned ( and therefore recovered how many times ). - Maybe an implicit event mentioning that the DAG was recovered and in which attempt it was recovered. Possibly add information on what state was recovered? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
