[
https://issues.apache.org/jira/browse/UIMA-4373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14532615#comment-14532615
]
Lou DeGenaro commented on UIMA-4373:
------------------------------------
bash-4.1$ ./viaducc -DDUCC_CLASS=reserve /bin/hostname
/home/degenaro/svn/apache/ducc/workspace/myhost/install/apache-uima-ducc-2.0.0-SNAPSHOT/bin/ducc_process_submit
--attach_console --process_memory_size 15 --scheduling_class reserve
--description viaducc --wait_for_completion --cancel_on_interrupt
--working_directory
/home/degenaro/svn/apache/ducc/workspace/myhost/install/apache-uima-ducc-2.0.0-SNAPSHOT/bin
--process_executable '/bin/hostname'
Managed Reservation 2 submitted.
id:2 location:27093@myhost
id:2 state:WaitingForResources
Deferred because resources are exhausted.
> Enhance monitor to report resource allocation status for reservations
> ---------------------------------------------------------------------
>
> Key: UIMA-4373
> URL: https://issues.apache.org/jira/browse/UIMA-4373
> Project: UIMA
> Issue Type: Improvement
> Components: DUCC
> Reporter: Eddie Epstein
> Assignee: Lou DeGenaro
> Fix For: 2.0.0-Ducc
>
>
> In DUCC v2.0 the resource allocation behavior for fixed shares has changed;
> instead of failing when an allocation cannot be made, the resource request is
> queued until it can be satisfied or until the request is canceled.
> The CLI needs to inform users when and why a request is queued. Moreover, the
> reason can change over time; for example, the user's allotment may be used up
> and the allocation blocked until user owned resources are freed, at which
> point the allocation may be waiting for pre-emptions to free up the required
> space. The CLI must inform when the reason changes.
> This CLI behavior update is needed for ducc_process_submit and ducc_reserve.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)