[
https://issues.apache.org/jira/browse/SAMZA-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14062455#comment-14062455
]
Chris Riccomini commented on SAMZA-109:
---------------------------------------
I would like to re-animate this ticket.
I took a brief look last week at this. I feel that this work should actually be
broken into two JIRAs:
# Step (1, 2, 3, 5) in the original list (eliminate LocalJobFactory, set log4j,
the system properties, -server, etc)
# Step (4) in the original list (have jobs log their container ID, and make
kill-job.sh use it)
I also think we should scrap my original idea bout doing string replacement in
environment variables (6, 7, 8). But it might be worth opening another JIRA
just to have the discussion.
The thing that I'm most interested is actually just steps 1, 2, 3, and 5, so
I'd propose moving step 4 into another JIRA, as well.
> Make task.opts easier to use
> ----------------------------
>
> Key: SAMZA-109
> URL: https://issues.apache.org/jira/browse/SAMZA-109
> Project: Samza
> Issue Type: Bug
> Components: container
> Affects Versions: 0.6.0
> Reporter: Chris Riccomini
> Assignee: Chinmay Soman
> Fix For: 0.8.0
>
>
> task.opts is a bit tricky to use right now.
> The most common thing that I see people want to do are:
> * Change the Xmx setting for their Samza containers.
> * Turn on a remote debugger.
> * Change garbage collector settings.
> Most of the time they do this in dev-mode (using LocalJobFactory).
> Changing task.opts is tricky for a number of reasons.
> 1. Changing task.opts at all eliminates all of the defaults. This means, if
> you set -Xmx, you lose all the defaults set in run-class.sh when no JVM_OPTS
> is set (log settings, Java system properties, etc).
> 2. LocalJobFactory uses ThreadJob by default, which doesn't even pay
> attention to task.opts (since it starts the container as a thread, not a new
> process).
> 3. If you manage to figure out how to switch LocalJobFactory to use
> ProcessJob (undocumented), you end up with the SamzaContainer running as a
> separate process with no way to kill it (the LocalJobRunner starts the
> ProcessJob, then exits).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
