[
http://opencast.jira.com/browse/MH-8148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=27947#comment-27947
]
Adam McKenzie commented on MH-8148:
-----------------------------------
I've assigned myself a sub task to get this done for 1.2 and trunk but in the
meantime do you have any ideas why max.concurrent is not limiting the number of
jobs that a worker is doing? When I am looking in that statistics pane I see
several jobs executing on the workers and when I run top on the workers it does
look like there are multiple mediapackages with different workflow ids being
processed by ffmpeg. I also have checked on the worker /system/console/config
to make sure that the configuration was being set properly and found:
PID = org.opencastproject.workflow.impl.WorkflowServiceImpl
BundleLocation = Unbound
max.concurrent = 1
service.pid = org.opencastproject.workflow.impl.WorkflowServiceImpl
Is it possible that this configuration value isn't really being used by workers
only admins?
> max.concurrent doesn't seem to actually set the number of jobs a worker is
> able to do.
> --------------------------------------------------------------------------------------
>
> Key: MH-8148
> URL: http://opencast.jira.com/browse/MH-8148
> Project: Matterhorn Project
> Issue Type: Bug
> Components: Architecture & Services
> Affects Versions: 1.2
> Reporter: Adam McKenzie
> Assignee: Adam McKenzie
> Priority: Critical
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
http://opencast.jira.com/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn
To unsubscribe please email
[email protected]
_______________________________________________
