Difference between revisions of "ServiceManager Guide"
Andrea.manzi (Talk | contribs) (→Known Issues) |
Andrea.manzi (Talk | contribs) |
||
| Line 33: | Line 33: | ||
* the search node should run at VRE level, manually we should add the VRE scope to the GHNProfile ''startScopes'' property. | * the search node should run at VRE level, manually we should add the VRE scope to the GHNProfile ''startScopes'' property. | ||
| + | |||
| + | |||
| + | == Executor and GenericWorker == | ||
Revision as of 13:30, 18 November 2013
This part of the guide is intended to cover the installation and configuration of gCube services that are not mentioned in the Administration guide. Mainly we refer to services that are not Enabling and that can be installed dynamically by the Infrastructure/VO Managers. The list includes also for each component known issues and specific configuration steps to follow.
Contents
Search
The installation of a Search Node in gCube is characterised by the installation of 2 web-services ( in the minimal configuration ) :
- SearchSystemService
- ExecutionEngineService
This is the minimal installation scenario but it's possible to enable distributed search as well and this will required the installation and configuration of several ExecutionEngineServices
HW requirements
The minimal installation requirements for a Search node are a Single CPU node with 2GB RAMm but it's more than recommended to have at least 3GB RAM on the node dedicated to the GHN.
Configuration
The SearchSystemService and ExecutionEngineService have to be automatically/manually deployed in a VRE scope. In addition if we want to configure the SearchSystemService to exploit the local ExecutionEngineService to run the queries ( minimal installation) we should configure the jndi service as follows:
- excludeLocal = false
- collocationThreshold = 0.3f
- complexPlanNumNodes = 800000
Known Issues
- The dynamic co-deployment of ExecutionEngine and Search service carries 2 RR configuration jars ( the one for search and the other for ExecutionEngine). The RR configuration for the ExecutionEngine should be removed manually.
- the rrcongprovider-service component is not shipeed with the Search service ( issues with circular dependencies), therefore must be installed manually.
- the search node should run at VRE level, manually we should add the VRE scope to the GHNProfile startScopes property.
