You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@griffin.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2019/09/30 13:12:00 UTC

[jira] [Work logged] (GRIFFIN-293) [Service] livy.need.queue=true

     [ https://issues.apache.org/jira/browse/GRIFFIN-293?focusedWorklogId=320484&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-320484 ]

ASF GitHub Bot logged work on GRIFFIN-293:
------------------------------------------

                Author: ASF GitHub Bot
            Created on: 30/Sep/19 13:11
            Start Date: 30/Sep/19 13:11
    Worklog Time Spent: 10m 
      Work Description: neveljkovic commented on pull request #541: GRIFFIN-293: [Service] livy.need.queue=true
URL: https://github.com/apache/griffin/pull/541
 
 
   This is how we fixed issue described in https://issues.apache.org/jira/browse/GRIFFIN-293
   Solution is deployed to our servers and works OK.
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 320484)
    Remaining Estimate: 0h
            Time Spent: 10m

> [Service] livy.need.queue=true
> ------------------------------
>
>                 Key: GRIFFIN-293
>                 URL: https://issues.apache.org/jira/browse/GRIFFIN-293
>             Project: Griffin
>          Issue Type: Bug
>    Affects Versions: 0.6.0
>            Reporter: Nevena Veljkovic
>            Priority: Critical
>             Fix For: 0.6.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> While using griffin in several productions environments, having x10 jobs starting at same hour, minute, second, we figured out that 2 (or more) concurrent griffin jobs are not submitted and executed to the end (the last was submitted multiple times, the rest never).
> example
>  2 jobs "beta_node_metrics_fact" and "beta_node_master_dimension_device", difference between them is 1 millisecond
> {code:java}
> 2019-09-28 14:00:37.090 INFO 2732 --- [ryBean_Worker-4] o.a.g.c.j.SparkSubmitJob [203] : {
>  "measure.type" : "griffin",
>  "id" : 60560,
>  "name" : "beta_node_metrics_fact",
> 2019-09-28 14:00:37.091 INFO 2732 --- [ryBean_Worker-5] o.a.g.c.j.SparkSubmitJob [203] : {
>  "measure.type" : "griffin",
>  "id" : 63751,
>  "name" : "beta_node_master_dimension_device",
> {code}
> livy submitted 2 jobs/tasks, both contained "beta_node_master_dimension_device"
> That's why decided to use setting "livy.need.queue=true".
>  During testing we figured out queueing does not work at all as LivyTaskSubmitHelper's member sparkSubmitJob was not instantiated
>  [https://github.com/apache/griffin/blob/master/service/src/main/java/org/apache/griffin/core/job/LivyTaskSubmitHelper.java#L64]
> We fixed this and continue with testing.
> During testing we figured out that curConcurrentTaskNum does not decrease finished tasks (state SUCCESS or DEAD).
>  [https://github.com/apache/griffin/blob/master/service/src/main/java/org/apache/griffin/core/job/JobServiceImpl.java#L632-L633]
> We fixed this also.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)