You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@uima.apache.org by bu...@apache.org on 2013/11/19 16:37:01 UTC

svn commit: r1543455 - in /uima/sandbox/uima-ducc/trunk: uima-ducc-cli/src/main/java/org/apache/uima/ducc/cli/ uima-ducc-duccdocs/src/site/tex/duccbook/part2/cli/ uima-ducc-duccdocs/src/site/tex/duccbook/part4/admin/

Author: burn
Date: Tue Nov 19 15:37:00 2013
New Revision: 1543455

URL: http://svn.apache.org/r1543455
Log:
UIMA-3439 Make defaults match the UI; rephrase rate as an interval rather than frequency; fix typos

Modified:
    uima/sandbox/uima-ducc/trunk/uima-ducc-cli/src/main/java/org/apache/uima/ducc/cli/IUiOptions.java
    uima/sandbox/uima-ducc/trunk/uima-ducc-duccdocs/src/site/tex/duccbook/part2/cli/ducc-services.tex
    uima/sandbox/uima-ducc/trunk/uima-ducc-duccdocs/src/site/tex/duccbook/part4/admin/ducc-properties.tex

Modified: uima/sandbox/uima-ducc/trunk/uima-ducc-cli/src/main/java/org/apache/uima/ducc/cli/IUiOptions.java
URL: http://svn.apache.org/viewvc/uima/sandbox/uima-ducc/trunk/uima-ducc-cli/src/main/java/org/apache/uima/ducc/cli/IUiOptions.java?rev=1543455&r1=1543454&r2=1543455&view=diff
==============================================================================
--- uima/sandbox/uima-ducc/trunk/uima-ducc-cli/src/main/java/org/apache/uima/ducc/cli/IUiOptions.java (original)
+++ uima/sandbox/uima-ducc/trunk/uima-ducc-cli/src/main/java/org/apache/uima/ducc/cli/IUiOptions.java Tue Nov 19 15:37:00 2013
@@ -199,7 +199,7 @@ public interface IUiOptions
             public String description() { return "Number of consecutive instance failures that will cause the service to be stopped."; }
             public String argname()     { return "integer"; }
             public String example()     { return null; }
-            public String deflt()       { return "5"; }
+            public String deflt()       { return "2"; }
             public String label()       { return "InstanceFailuresLimit"; }
         },   
         JobId { 

Modified: uima/sandbox/uima-ducc/trunk/uima-ducc-duccdocs/src/site/tex/duccbook/part2/cli/ducc-services.tex
URL: http://svn.apache.org/viewvc/uima/sandbox/uima-ducc/trunk/uima-ducc-duccdocs/src/site/tex/duccbook/part2/cli/ducc-services.tex?rev=1543455&r1=1543454&r2=1543455&view=diff
==============================================================================
--- uima/sandbox/uima-ducc/trunk/uima-ducc-duccdocs/src/site/tex/duccbook/part2/cli/ducc-services.tex (original)
+++ uima/sandbox/uima-ducc/trunk/uima-ducc-duccdocs/src/site/tex/duccbook/part2/cli/ducc-services.tex Tue Nov 19 15:37:00 2013
@@ -467,7 +467,7 @@ ducc_services --modify UIMA-AS:Service23
       Below is a sample service query.
 
       The service with endpoint {\tt UIMA-AS:FixedSleepAE\_5:tcp://bobmach:61617} is a 
-      registered service, whose registered numeric id is 2. It is registered for two instances and 
+      registered service, whose registered numeric id is 2. It was registered by bob for two instances and 
       no autostart. Since it is not autostarted, it will be terminated when it is no longer used. It 
       will linger for 5 seconds after the last referencing job completes, in case a subsequent job 
       that uses it enters the system (not a realistic linger time!). It has two active
@@ -478,15 +478,15 @@ ducc_services --modify UIMA-AS:Service23
 \begin{verbatim}
 
 Service: UIMA-AS:FixedSleepAE_5:tcp://bobmach291:61617 
-Service Class : Registered as ID 2 instances[2] linger[5] 
-Implementors : 9 8 
-References : 1 5 
-Dependencies : none 
-Service State : Available 
-Ping Active : true 
-Autostart : false 
-Manual Stop : false 
-Queue Statistics: 
+   Service Class : Registered as ID 2 Owner[bob] instances[2] linger[5000] 
+   Implementors : 9 8 
+   References : 1 5 
+   Dependencies : none 
+   Service State : Available 
+   Ping Active : true 
+   Autostart : false 
+   Manual Stop : false 
+   Queue Statistics: 
 Consum Prod Qsize minNQ maxNQ expCnt inFlgt  DQ  NQ Disp 
     52   44     0     0     3      0      0 402 402  402 
 \end{verbatim}

Modified: uima/sandbox/uima-ducc/trunk/uima-ducc-duccdocs/src/site/tex/duccbook/part4/admin/ducc-properties.tex
URL: http://svn.apache.org/viewvc/uima/sandbox/uima-ducc/trunk/uima-ducc-duccdocs/src/site/tex/duccbook/part4/admin/ducc-properties.tex?rev=1543455&r1=1543454&r2=1543455&view=diff
==============================================================================
--- uima/sandbox/uima-ducc/trunk/uima-ducc-duccdocs/src/site/tex/duccbook/part4/admin/ducc-properties.tex (original)
+++ uima/sandbox/uima-ducc/trunk/uima-ducc-duccdocs/src/site/tex/duccbook/part4/admin/ducc-properties.tex Tue Nov 19 15:37:00 2013
@@ -178,7 +178,7 @@
          \end{description} 
 
        \item[ducc.cli.httpclient.sotimeout] \hfill \\
-         This is the timeout used by the CLI to communicate with DUCC, in millisseconds. If no 
+         This is the timeout used by the CLI to communicate with DUCC, in milliseconds. If no 
          response is heard within this time, the request times out and is aborted. When set to 0 (the 
          default), the request never times out. 
          \begin{description}
@@ -264,6 +264,9 @@
        \item[ducc.driver.jvm.args] \hfill \\
          If enabled, the arguments here are automatically added to the JVM arguments specified for 
          the Job Driver process. 
+
+         Note: if the user-supplied JVM arguments contain a -Xmx entry then 
+         any -Xmx value specified here will be ignored.
          \begin{description}
            \item[Default] (unconfigured) 
            \item[Type] Local 
@@ -355,9 +358,9 @@
           \end{description}
 
 
-       \item[ducc.submit.threads.limit] \hfill \\
-         This enforces a maximum number of threads per job, amortized over all the processes. No 
-         job will have more threads than this dispatched. This limit is disabled by default. 
+       \item[ducc.threads.limit] \hfill \\
+         This enforces a maximum number of pipeline threads per job, over all its processes. No 
+         job will have more active work-items than this dispatched. This limit is disabled by default. 
 
          The value represents the size of the underlying CAS pool in the Job Driver and therefore
          is related to the size of the Job Driver heap and the real memory consumed by JD.  If
@@ -368,10 +371,10 @@
            \item[Type] Local 
          \end{description}
 
-       \item[ducc.submit.environment.propagated] \hfill \\
+       \item[ducc.environment.propagated] \hfill \\
          This specifies the environmental variables whose values will be merged with the
          user-specified environment option on job, process and service submissions.  A typical setting
-         might be: USER HOME
+         might be: USER HOME LANG
 
          \begin{description}
            \item[Default] (unconfigured) 
@@ -513,7 +516,8 @@
           
 
         \item[ducc.jd.state.publish.rate] \hfill \\
-          The frequency in milliseconds that JD publishes its state to the Orchestrator. A higher rate 
+          The interval in milliseconds between JD state publications to the Orchestrator.
+          A higher rate (smaller number)
           may slightly increase system response but will increase network load. A lower rate will 
           somewhat decrease system response and lower network load. 
           \begin{description}
@@ -672,10 +676,10 @@
         
       \item[ducc.sm.default.linger] \hfill \\
         This is the length of time, in milliseconds, that the SM allows a service to remain alive after 
-        all referenceing jobs have exited. If no new job enters the system by the time this time has 
+        all jobs that reference it have exited. If no new job referencing it enters the system before this time has 
         expired, the SM stops the service. 
         \begin{description}
-          \item[Default Value] 30000
+          \item[Default Value] 300000
           \item[Type] Tuning 
         \end{description}
         
@@ -685,7 +689,7 @@
         will disable autostart for the service.  It may be overridden by the service
         registration's {\em instance\_failures\_limit} parameter.
         \begin{description}
-          \item[Default Value] 5
+          \item[Default Value] 2
           \item[Type] Tuning 
         \end{description}
         
@@ -738,7 +742,7 @@
         \end{description} 
         
       \item[ducc.orchestrator.state.publish.rate] \hfill \\
-        This is the frequency in milliseconds that the Orchestrator publishes its non-abbreviated 
+        The interval in milliseconds between Orchestrator publications of its non-abbreviated  
         state. 
         \begin{description}
           \item[Default Value] 15000 
@@ -762,15 +766,15 @@
         \end{description} 
         
       \item[ducc.orchestrator.abbreviated.state.publish.rate] \hfill \\
-        This is the frequency in milliseconds that the Orchestrator publishes its abbreviated state. 
+        The interval in milliseconds between Orchestrator publications of its abbreviated state. 
         \begin{description}
-          \item[Default Valu] 15000 
+          \item[Default Value] 15000 
           \item[Type] Private
         \end{description} 
 
       \item[ducc.orchestrator.maintenance.rate] \hfill \\
-        This is the frequency in milliseconds that the Orchestrator checks and updates history and 
-        state. 
+        This is the interval in milliseconds between Orchestrator maintenance cycles, which check
+        and update history and state. 
         \begin{description}
           \item[Default Value] 60000 
           \item[Type] Tuning 
@@ -828,8 +832,7 @@
           \end{description}
           
         \item[ducc.rm.state.publish.rate] \hfill \\
-          This is the rate, in milliseconds, at which the Resource Manager publishes its state to the 
-          Orchestrator. 
+          The interval in milliseconds between Resource Manager state publications to the Orchestrator.
 
           This can directly affect user response.  For small clusters a value of 10000 is often acceptable
           and results in faster response.  On larger clusters the value should be raised to around
@@ -1084,9 +1087,9 @@
           \end{description}
          
         \item[ducc.agent.node.metrics.publish.rate] \hfill \\
-          This is the rate at which node metrics updates are published in milliseconds.   Every
-          agent publishes its metrics at this rate.  On large clusters, a high rate (small 
-          value for the rate) can be a burdon on the network.
+          The interval in milliseconds between node metric publications.
+          Every agent publishes its updates at this rate.  On large clusters, a high rate (small 
+          interval) can be a burden on the network.
 
           Note: the Resource Manager uses the data in the node metrics for scheduling.
           \begin{description}
@@ -1111,7 +1114,7 @@
           \end{description}
           
         \item[ducc.agent.node.inventory.publish.rate] \hfill \\
-          This is the rate at which node inventory updates are published in milliseconds. 
+          The interval in milliseconds between node inventory publications.
 
           If the inventory has not changed since the last update the agent bypasses sending the 
           update, up to a maximum of ducc.agent.node.inventory.publish.rate.skip times. 
@@ -1320,7 +1323,7 @@
         \end{description}
         
       \item[ducc.pm.state.publish.rate] \hfill \\
-        This is the rate at which the process manager publishes its heartbeat, in milliseconds. 
+        The interval in milliseconds between process manager heartbeat publications.
         \begin{description}
         \item[Default Value] 25000 
         \item[Type] Private