Unknown macro: {next_previous_link3}
Skip to end of metadata
  • Created by Former user, last modified by Former user on Jan 30, 2019
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

This section explains how to troubleshoot exceptions that occur when indexing activities are carried out.

AnalyticsTableNotAvailableException

Sample Error Log
TID: [-1] [] [2018-02-13 04:49:40,345] ERROR {org.wso2.carbon.analytics.dataservice.core.indexing.IndexNodeCoordinator} -  Error in processing staging index data: Error in processing index staging entry: [-1234:NEW_CUSTOMERS_BY_QUARTER_PRODUCT_AND_POD] does not exist {org.wso2.carbon.analytics.dataservice.core.indexing.IndexNodeCoordinator}
org.wso2.carbon.analytics.datasource.commons.exception.AnalyticsException: Error in processing index staging entry: [-1234:NEW_CUSTOMERS_BY_QUARTER_PRODUCT_AND_POD] does not exist
	at org.wso2.carbon.analytics.dataservice.core.indexing.IndexNodeCoordinator.processStagingEntry(IndexNodeCoordinator.java:961)
	at org.wso2.carbon.analytics.dataservice.core.indexing.IndexNodeCoordinator.access$600(IndexNodeCoordinator.java:69)
	at org.wso2.carbon.analytics.dataservice.core.indexing.IndexNodeCoordinator$StagingDataIndexWorker.run(IndexNodeCoordinator.java:997)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
OccurenceWhen the INSERT OVERWRITE operation is carried out.
Possible Reasons

The corruption of meta information and indexing that could have resulted from one of the following:

  • Deployments or the removal of deployments in the nodes of the DAS setup.
  • Configuration changes in the DAS nodes of the setup/
  • Creating/deleting tables in the event store or the process store.
Recommended Action

To resolve this issue, reindex your data following the steps below:

  1. Shut down all the DAS nodes in your deployment.

  2. Truncate the following tables.

    Table names are encoded in characters that cannot be read by humans for all database types other than HBase and Cassandra. Therefore, if the database type is not HBase or Cassandra, you need to use the encoded versions of these table names depending on the database type when performing this step.


    • ANX_X1000__INDEX_STAGING_DATA_*
    • IDX_X1000__INDEX_STAGING_DATA_*
     

  3. Drop all the tables with names that start with ANX and IDX such as the examples given below.

    Table names are encoded in characters that cannot be read by humans for all database types other than HBase and Cassandra. Therefore, this step is relevant only if the database type used is HBase or Cassandra because the table names given below can only exist for these two database types.


    • ANX_X1000__INDEX_STAGING_DATA_*
    • IDX_X1000__INDEX_STAGING_DATA_*
  4. For each node, remove all the index data stored in the <DAS_HOME>/repository/data directory.
  5. Restart the DAS nodes.

For more information about indexing, see Indexing Overview.

  • No labels
Unknown macro: {next_previous_links2}