[jira] [Created] (GOBBLIN-654) Fix the argument order of JobStatusRetriever APIs to reflect actual usage.

2018-12-11 Thread Sudarshan Vasudevan (JIRA)
Sudarshan Vasudevan created GOBBLIN-654:
---

 Summary: Fix the argument order of JobStatusRetriever APIs to 
reflect actual usage.
 Key: GOBBLIN-654
 URL: https://issues.apache.org/jira/browse/GOBBLIN-654
 Project: Apache Gobblin
  Issue Type: Bug
  Components: gobblin-service
Affects Versions: 0.15.0
Reporter: Sudarshan Vasudevan
Assignee: Sudarshan Vasudevan
 Fix For: 0.15.0


The argument order for JobStatusRetriever#getJobStatusesForFlowExecution() do 
not match the actual usage in the implementation. This ticket fixes the 
argument order for the API.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (GOBBLIN-653) Create JobSucceededTimer tracking event to accurately track successful Gobblin jobs.

2018-12-11 Thread Hung Tran (JIRA)


 [ 
https://issues.apache.org/jira/browse/GOBBLIN-653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hung Tran resolved GOBBLIN-653.
---
Resolution: Fixed

Issue resolved by pull request #2522
[https://github.com/apache/incubator-gobblin/pull/2522]

> Create JobSucceededTimer tracking event to accurately track successful 
> Gobblin jobs.
> 
>
> Key: GOBBLIN-653
> URL: https://issues.apache.org/jira/browse/GOBBLIN-653
> Project: Apache Gobblin
>  Issue Type: Improvement
>  Components: gobblin-metrics
>Affects Versions: 0.15.0
>Reporter: Sudarshan Vasudevan
>Assignee: Sudarshan Vasudevan
>Priority: Major
> Fix For: 0.15.0
>
>
> The JobCompleteTimer event is not sufficient to track successfully completed 
> Gobblin jobs, since this timer event is emitted even in case of failed jobs. 
> We introduce a new timing event that accurately tracks successful job 
> completions. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (GOBBLIN-652) gobblin cluster doesn't have helix related metrics

2018-12-11 Thread Hung Tran (JIRA)


 [ 
https://issues.apache.org/jira/browse/GOBBLIN-652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hung Tran resolved GOBBLIN-652.
---
   Resolution: Fixed
Fix Version/s: 0.15.0

Issue resolved by pull request #2521
[https://github.com/apache/incubator-gobblin/pull/2521]

> gobblin cluster doesn't have helix related metrics
> --
>
> Key: GOBBLIN-652
> URL: https://issues.apache.org/jira/browse/GOBBLIN-652
> Project: Apache Gobblin
>  Issue Type: Improvement
>Reporter: Kuai Yu
>Assignee: Kuai Yu
>Priority: Major
> Fix For: 0.15.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (GOBBLIN-653) Create JobSucceededTimer tracking event to accurately track successful Gobblin jobs.

2018-12-11 Thread Sudarshan Vasudevan (JIRA)
Sudarshan Vasudevan created GOBBLIN-653:
---

 Summary: Create JobSucceededTimer tracking event to accurately 
track successful Gobblin jobs.
 Key: GOBBLIN-653
 URL: https://issues.apache.org/jira/browse/GOBBLIN-653
 Project: Apache Gobblin
  Issue Type: Improvement
  Components: gobblin-metrics
Affects Versions: 0.15.0
Reporter: Sudarshan Vasudevan
Assignee: Sudarshan Vasudevan
 Fix For: 0.15.0


The JobCompleteTimer event is not sufficient to track successfully completed 
Gobblin jobs, since this timer event is emitted even in case of failed jobs. We 
introduce a new timing event that accurately tracks successful job completions. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (GOBBLIN-652) gobblin cluster doesn't have helix related metrics

2018-12-11 Thread Kuai Yu (JIRA)
Kuai Yu created GOBBLIN-652:
---

 Summary: gobblin cluster doesn't have helix related metrics
 Key: GOBBLIN-652
 URL: https://issues.apache.org/jira/browse/GOBBLIN-652
 Project: Apache Gobblin
  Issue Type: Improvement
Reporter: Kuai Yu
Assignee: Kuai Yu






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (GOBBLIN-651) Ensure ordered delivery of Kafka events from KeyValueProducerPusher for kafka-08.

2018-12-11 Thread Hung Tran (JIRA)


 [ 
https://issues.apache.org/jira/browse/GOBBLIN-651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hung Tran resolved GOBBLIN-651.
---
Resolution: Fixed

Issue resolved by pull request #2520
[https://github.com/apache/incubator-gobblin/pull/2520]

> Ensure ordered delivery of Kafka events from KeyValueProducerPusher for 
> kafka-08. 
> --
>
> Key: GOBBLIN-651
> URL: https://issues.apache.org/jira/browse/GOBBLIN-651
> Project: Apache Gobblin
>  Issue Type: Improvement
>  Components: gobblin-kafka
>Affects Versions: 0.15.0
>Reporter: Sudarshan Vasudevan
>Assignee: Sudarshan Vasudevan
>Priority: Major
> Fix For: 0.15.0
>
>
> Same as [GOBBLIN-650|https://issues.apache.org/jira/browse/GOBBLIN-650], the 
> config needs to be applied to kafka-08 client as well.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (GOBBLIN-651) Ensure ordered delivery of Kafka events from KeyValueProducerPusher for kafka-08.

2018-12-11 Thread Sudarshan Vasudevan (JIRA)
Sudarshan Vasudevan created GOBBLIN-651:
---

 Summary: Ensure ordered delivery of Kafka events from 
KeyValueProducerPusher for kafka-08. 
 Key: GOBBLIN-651
 URL: https://issues.apache.org/jira/browse/GOBBLIN-651
 Project: Apache Gobblin
  Issue Type: Improvement
  Components: gobblin-kafka
Affects Versions: 0.15.0
Reporter: Sudarshan Vasudevan
Assignee: Sudarshan Vasudevan
 Fix For: 0.15.0


Same as [GOBBLIN-650|https://issues.apache.org/jira/browse/GOBBLIN-650], the 
config needs to be applied to kafka-08 client as well.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (GOBBLIN-650) Ensure ordered delivery of Kafka events from KeyValueProducerPusher.

2018-12-11 Thread Hung Tran (JIRA)


 [ 
https://issues.apache.org/jira/browse/GOBBLIN-650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hung Tran resolved GOBBLIN-650.
---
Resolution: Fixed

Issue resolved by pull request #2519
[https://github.com/apache/incubator-gobblin/pull/2519]

> Ensure ordered delivery of Kafka events from KeyValueProducerPusher.
> 
>
> Key: GOBBLIN-650
> URL: https://issues.apache.org/jira/browse/GOBBLIN-650
> Project: Apache Gobblin
>  Issue Type: Improvement
>  Components: gobblin-kafka
>Affects Versions: 0.15.0
>Reporter: Sudarshan Vasudevan
>Assignee: Sudarshan Vasudevan
>Priority: Trivial
> Fix For: 0.15.0
>
>
> To guarantee that the messages emitted by the KeyValueProducerPusher are 
> ordered in the presence of retries, we need to set the config for maximum in 
> flight requests per connection to 1. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (GOBBLIN-650) Ensure ordered delivery of Kafka events from KeyValueProducerPusher.

2018-12-11 Thread Sudarshan Vasudevan (JIRA)
Sudarshan Vasudevan created GOBBLIN-650:
---

 Summary: Ensure ordered delivery of Kafka events from 
KeyValueProducerPusher.
 Key: GOBBLIN-650
 URL: https://issues.apache.org/jira/browse/GOBBLIN-650
 Project: Apache Gobblin
  Issue Type: Improvement
  Components: gobblin-kafka
Affects Versions: 0.15.0
Reporter: Sudarshan Vasudevan
Assignee: Sudarshan Vasudevan
 Fix For: 0.15.0


To guarantee that the messages emitted by the KeyValueProducerPusher are 
ordered in the presence of retries, we need to set the config for maximum in 
flight requests per connection to 1. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)