...
This section covers the best practices to follow when applying WUM updates to DAS. The main factors to consider are as follows.
| Info |
|---|
The following guidelines applicable only if you replace you DAS binary pack with a new pack to which the WUM updates are applied. For more information about this method of applying WUM updates, see WSO2 Admin Guide - Applying Wum Updates Manually. If you follow this method, you need to move the WSO2 DAS pack that is updated with the WUM updates to the production envronment before applying these best practices. For more informtion, see WSO2 Admin Guide - Apply WUM Updated Products Using Automation. |
| Excerpt | ||
|---|---|---|
| ||
Check on this.
|
| Table of Contents | ||||
|---|---|---|---|---|
|
...
Information relating to the Shard allocation is maintained in the <DAS_HOME>/repository/conf/analyticsdata/local-shard-allocation-config.conf file. This file stores the shard number along with its state (that can be INIT or NORMAL). The INIT is the initial state. Usually this state cannot be seen from outside. This is because the INIT state changes to the NORMAL state once the server starts. If the indexing node is running, the state of shards should be NORMAL and not INIT. The NORMAL state denotes that the indexing node has started indexing. For detailed information about the shard allocation, see Indexing Overview - Indexing Architecture.
Before you discard the old DAS instance, you must take a backup of the <DAS_HOME>/repository/conf/analyticsdata/local-shard-allocation-config.conf file, and copy is back to the same location in the DAS binary pack that is updated with the WUM updates.