DbProxy

  1. When the connection to the back-end database server fails, a client connected through a proxy appears to hang. This is because the default settings on the client side will retry the connection every five minutes for up to one hour. For the HLT, we need to change these parameters to something more reasonable (that makes the system succeed or fail immediately).

M2OProxy

  1. The executable is still running out of Andy's home directory rather than the release. To fix this, several changes need to be made to the setup-initial.data.xml files:
    1. include files change 
      <include>
- <file path="daq/sw/m2o-repository.data.xml"/>
+  <file path="HLTRelease/sw/HLT_SW_Repository.data.xml"/>
</include>
    2. application class changed, binary comes from HLT repository: 
      - <obj class="Application" id="M2O_Proxy">
+ <obj class="InfrastructureApplication" id="M2O_Proxy">
- <rel name="Program">"Binary" "m2o-proxy-14.2.11"</rel>
+  <rel name="Program">"Binary" "m2o-proxy"</rel>
    3. move application from "Applications" to "Infrastructure": 
      <obj class="OnlineSegment" id="setup-initial">
<rel name="Applications" num="..">
- "Application" "M2O_Proxy"
</rel>
<rel name="Infrastructure" num="..">
+   "InfrastructureApplication" "M2O_Proxy"
</rel>
    4. expand 
      ${CMTCONFIG}
      in the HLT environment: 
      <obj class="OnlineSegment" id="setup-initial">
<rel name="Parameters" num="..">
+   "VariableSet" "HLT-Parameters"
</rel>
  2. Need to test if the proxy is properly started/restarted by the initial partition under various conditions:
    1. when the initial partition is restarted
    2. when the node that the proxy runs on (pc-tdq-onl-10) is rebooted
    3. when the proxy dies (crashes or is killed) for some reason
  • No labels