[
https://issues.apache.org/jira/browse/GOBBLIN-707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Sen updated GOBBLIN-707:
----------------------------
Description:
gobblin supports multiple modes of executions ( CLI, Standalone,
cluster-master, cluster-worker, AWS, YARN, MR ) and there is a individual
script for each of them.
Having individual script introduces lot of issues
# all scripts handles gobblin variables, user parameters differently, and its
highly inconsistent among various different gobblin scripts
# functionality around start, stop, status checking and handling PID's among
lot of other things, varies vastly as per the implementation of the script.
# features like GC & JVM params, log4j file selection, classpath calculation,
etc... exists in some gobblin scripts but not all, adding to inconsistent user
experience.
# maintaining total 13 script would be too much effort.
All the gobblin scripts share lot of common code to handle params, start, stop
services, status checks, pid handling, etc... combining all the scripts into 1
not only makes maintenance easier but also brings clarity and consistency.
1. there can be one gobblin.sh script
{{gobblin.sh <command> <params>}}
{{gobblin.sh <service-name> <start|stop|status>}}
{{commands values: admin, cli, statestore-check, statestore-clean,
historystore-manager}}
{{service values: standalone, cluster-master, cluster-worker, aws, yarn, mr,
service}}
2. Also configs needs to be structured and deduped accordingly.
was:
gobblin supports multiple modes of executions ( CLI, Standalone,
cluster-master, cluster-worker, AWS, YARN, MR ) and there is a individual
script for each of them.
1. there can be one gobblin.sh script
{{gobblin.sh <command> <params>}}
{{gobblin.sh <service-name> <start|stop|status>}}
{{commands values: admin, cli, statestore-check, statestore-clean,
historystore-manager}}
{{service values: standalone, cluster-master, cluster-worker, aws, yarn, mr,
service}}
2. Also configs needs to be structured and deduped accordingly.
> combine & standardize all gobblin scripts into one master script &
> restructure configs accordingly
> --------------------------------------------------------------------------------------------------
>
> Key: GOBBLIN-707
> URL: https://issues.apache.org/jira/browse/GOBBLIN-707
> Project: Apache Gobblin
> Issue Type: Improvement
> Reporter: Jay Sen
> Priority: Major
> Time Spent: 3h 10m
> Remaining Estimate: 0h
>
> gobblin supports multiple modes of executions ( CLI, Standalone,
> cluster-master, cluster-worker, AWS, YARN, MR ) and there is a individual
> script for each of them.
> Having individual script introduces lot of issues
> # all scripts handles gobblin variables, user parameters differently, and
> its highly inconsistent among various different gobblin scripts
> # functionality around start, stop, status checking and handling PID's among
> lot of other things, varies vastly as per the implementation of the script.
> # features like GC & JVM params, log4j file selection, classpath
> calculation, etc... exists in some gobblin scripts but not all, adding to
> inconsistent user experience.
> # maintaining total 13 script would be too much effort.
>
> All the gobblin scripts share lot of common code to handle params, start,
> stop services, status checks, pid handling, etc... combining all the scripts
> into 1 not only makes maintenance easier but also brings clarity and
> consistency.
>
> 1. there can be one gobblin.sh script
> {{gobblin.sh <command> <params>}}
> {{gobblin.sh <service-name> <start|stop|status>}}
> {{commands values: admin, cli, statestore-check, statestore-clean,
> historystore-manager}}
> {{service values: standalone, cluster-master, cluster-worker, aws, yarn, mr,
> service}}
> 2. Also configs needs to be structured and deduped accordingly.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
