Hi,
You are right that ducc.agent.node.metrics.fake.memory.size will override
the agent's computation of total usable memory. This must be set as a java
property on the agent. To set this for all agents, add the following line
to site.ducc.properties in the resources folder and restart DUCC.
Nelson, using the same snapshot I see a different behavior of UIMA-AS
service when a broker is bounced:
12:21:35.452 - 27:
org.apache.uima.adapter.jms.activemq.UimaDefaultMessageListenerContainer.handleTempQueueFailure:
WARNING: Service: Test Aggregate TAE Runtime Exception
12:21:35.452 - 27:
Hi Eddie,
ok, I will try to explain with more detail, maybe this is not how ducc
is being used normally. We want to set up some nodes which are not
exclusively used for ducc. For example, one of the nodes may have 100
GB, but we want the usable memory for ducc to only be 50 GB, not all
I tried the snapshot that you gave me, and I understand perfectly the
explanation of recovery queue that you explain, but to me not work,
and y get the same behavior. With the last snapshop, the uima-as log
never show recovery of new queue after restart broker (restart =
execute
