You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@griffin.apache.org by "Lionel Liu (JIRA)" <ji...@apache.org> on 2018/05/16 05:23:00 UTC
[jira] [Updated] (GRIFFIN-79) Some tasks griffin ops needs to
optimized for cluster env
[ https://issues.apache.org/jira/browse/GRIFFIN-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lionel Liu updated GRIFFIN-79:
------------------------------
Fix Version/s: (was: 0.2.0-incubating)
1.0.0-incubating
> Some tasks griffin ops needs to optimized for cluster env
> ---------------------------------------------------------
>
> Key: GRIFFIN-79
> URL: https://issues.apache.org/jira/browse/GRIFFIN-79
> Project: Griffin (Incubating)
> Issue Type: Task
> Reporter: William Guo
> Assignee: William Guo
> Priority: Major
> Fix For: 1.0.0-incubating
>
>
> Hi there,
> Below are meeting notes for 2018 Q1:
> Issues:
> 1. Data recovery : when job hangs (dq=0 or stops ), data loss, after
> job is restarted
> 2. HDFS maintenance: griffin job no outputs, because it fails to
> connect to hadoop
> 3. when count priority job hangs (dq=0 or stops ): may be caused by app
> memory leak issue
> 4. Job runs unstable, too much to restart jobs
> Features:
> 1. Multi-connector support
> 2. Uniqueness
> 3. Tagged-metrics
> 4. Freshness
> 5. Validity
> Best Regards,
> Jenny
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)