...
Improvement Area | Performance Recommendations | ||||||||
---|---|---|---|---|---|---|---|---|---|
Data receiver nodes |
| ||||||||
Analyzer nodes | Xms1024m -Xmx1024m -XX:MaxPermSize=512m | ||||||||
Dashboard nodes | Xms1024m -Xmx1024m -XX:MaxPermSize=512m | ||||||||
Hadoop nodes |
| ||||||||
Cassandra nodes |
For more information see Apache Cassandra 1.0 Documentation. | ||||||||
Memory size of Hive | In order to increase the memory size of Hive try the following configurations:
|
WSO2 Carbon platform-level settings
In multitenant mode, the WSO2 Carbon runtime limits the thread execution time. That is, if a thread is stuck or taking a long time to process, Carbon detects such threads, interrupts and stops them. Note that Carbon prints the current stack trace before interrupting the thread. This mechanism is implemented as an Apache Tomcat valve. Therefore, it should be configured in the <PRODUCT_HOME>/repository/conf/tomcat/catalina-server.xml
file as shown below.
Code Block | ||
---|---|---|
| ||
<Valve className="org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve" threshold="600"/> |
- The
className
is the Java class used for the implementation. Set it toorg.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve
. - The
threshold
gives the minimum duration in seconds after which a thread is considered stuck. The default value is 600 seconds.
JVM settings
When an XML element has a large number of sub-elements and the system tries to process all the sub-elements, the system can become unstable due to a memory overhead. This is a security risk.
To avoid this issue, you can define a maximum level of entity substitutions that the XML parser allows in the system. You do this using the entity expansion limit
attribute that is in the <DAS_HOME>/bin/wso2server.bat
file (for Windows) or the <DAS_HOME>/bin/wso2server.sh
file (for Linux/Solaris). The default entity expansion limit is 64000.
Code Block | ||
---|---|---|
| ||
-DentityExpansionLimit=100000 |
In a clustered environment, the entity expansion limit has no dependency on the number of worker nodes