Versions Compared

Old Version 14

changes.mady.by.user Former user

Saved on

compared with

New Version Current

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Issues relating to the disk space

OccurenceDisk space related issues occur when a high volume of data is stored in the databases.
Possible Reasons
  • Tables with the ANX__8 prefix contain a huge amount of data and it takes the majority of the DB size.
  • The known issue in Oracle databases where the previously used disk space cannot be reclaimed after deleting data from database tables
Recommended Action
To resolve this issue, reindex
  • Reindex your data by following the steps below:
    1. Shut down all the DAS nodes in your deployment.
    2. Delete all the contents of the <DAS_HOME>repository/data directory except the local-shard-allocation-config.conf file.
    3. In the WSO2_ANALYTICS_EVENT_STORE_DB database, delete all the tables with the ANX__8 prefix.

    4. Open the <DAS_HOME>repository/data/local-shard-allocation-config.conf file, and change the status of all the shards from NORMAL top INIT, so that the content looks as follows.

      Code Block
      languagejs
      0,INIT
1,INIT
2,INIT
3,INIT
4,INIT
5,INIT
      Tip

      If you find any other content in the local-shard-allocation-config.conf file, remove it.

    5. Restart the DAS nodes. Once the re-indexing is completed, the status of the shards in the local-shard-allocation-config.conf file changes from INIT to NORMAL.
  • If you are using the Oracle database type, you need to shrink the database to reclaim the disk space previously used by the deleted data. To do this, follow the steps provided in this Oracle community discussion.


For more information about indexing, see Indexing Overview.