You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@falcon.apache.org by "Arpit Gupta (JIRA)" <ji...@apache.org> on 2013/10/31 02:40:28 UTC
[jira] [Updated] (FALCON-162) Update falcon scripts to let the user
set the log and pid locations.
[ https://issues.apache.org/jira/browse/FALCON-162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arpit Gupta updated FALCON-162:
-------------------------------
Attachment: FALCON-162.patch
Here is the first revision. I still need to add a dummy falcon-env.sh in the config.
This will allow user to change log dirs, pid dir set java home, set heap size etc.
I have tested this and made sure all the same defaults are there that were there before.
> Update falcon scripts to let the user set the log and pid locations.
> --------------------------------------------------------------------
>
> Key: FALCON-162
> URL: https://issues.apache.org/jira/browse/FALCON-162
> Project: Falcon
> Issue Type: Bug
> Reporter: Arpit Gupta
> Assignee: Arpit Gupta
> Attachments: FALCON-162.patch
>
>
> Current falcon scripts hard code the location of the log and the pid dirs. Instead if we added the ability to source a falcon-env.sh which the user could provide then the user can overwrite these locations to some thing else.
> This would also allow the user a way to set JAVA_HOME and other env vars in a file rather than doing it in a shell. This is something similar to how hadoop works.
> Along with this change i also plan on changing the classpath to list dir/* instead of every jar file. Again this is similar to what hadoop 2 does.
--
This message was sent by Atlassian JIRA
(v6.1#6144)