WSO2DAS版本:3.0.1
在查看最低高可用性部署文档后,我设置了WSO2DAS。 (https://docs.wso2.com/display/CLUSTER44x/Minimum+High+Availability+Deployment+-+DAS+3.0.1)
和使用mariaDB的DAS产品。 mariaDB有两个数据库(WSO2_ANALYTICS_EVENT_STORE_DB,WSO2_ANALYTICS_PROCESSED_DATA_STORE_DB) 数据库中的表在请求api之后有数据。
最后。我在查看清除数据文档后设置了清除配置。 (https://docs.wso2.com/display/DAS301/Purging+Data)
更改了属性中的配置,如下所示。
<analytics-dataservice-configuration>
<!-- The name of the primary record store -->
<primaryRecordStore>EVENT_STORE</primaryRecordStore>
<!-- Analytics Record Store - properties related to record storage implementation -->
<analytics-record-store name="EVENT_STORE">
<implementation>org.wso2.carbon.analytics.datasource.rdbms.RDBMSAnalyticsRecordStore</implementation>
<properties>
<property name="datasource">WSO2_ANALYTICS_EVENT_STORE_DB</property>
<property name="category">large_dataset_optimized</property>
</properties>
</analytics-record-store>
<analytics-record-store name = "PROCESSED_DATA_STORE">
<implementation>org.wso2.carbon.analytics.datasource.rdbms.RDBMSAnalyticsRecordStore</implementation>
<properties>
<property name="datasource">WSO2_ANALYTICS_PROCESSED_DATA_STORE_DB</property>
<property name="category">large_dataset_optimized</property>
</properties>
</analytics-record-store>
<!-- The data indexing analyzer implementation -->
<analytics-lucene-analyzer>
<implementation>org.apache.lucene.analysis.standard.StandardAnalyzer</implementation>
</analytics-lucene-analyzer>
<!-- The number of index data replicas the system should keep, for H/A, this should be at least 1, e.g. the value 0 means
there aren't any copies of the data -->
<indexReplicationFactor>1</indexReplicationFactor>
<!-- The number of index shards, should be equal or higher to the number of indexing nodes that is going to be working,
ideal count being 'number of indexing nodes * [CPU cores used for indexing per node]' -->
<shardCount>6</shardCount>
<!-- The amount of index data (in bytes) to be processed at a time by a shard index worker. Minimum value is 1000. -->
<shardIndexRecordBatchSize>20971520</shardIndexRecordBatchSize>
<!-- The interval in milliseconds, which a shard index processing worker thread will sleep during index processing operations. This setting
along with the 'shardIndexRecordBatchSize' setting can be used to increase the final index batched data amount the indexer processes
at a given time. Usually, higher the batch data amount, higher the throughput of the indexing operations, but will have a higher latency
of record insertion to indexing. Minimum value of this is 10, and a maximum value is 60000 (1 minute). -->
<shardIndexWorkerInterval>1500</shardIndexWorkerInterval>
<!-- Data purging related configuration -->
<analytics-data-purging>
<!-- Below entry will indicate purging is enable or not. If user wants to enable data purging for cluster then this property
need to be enable in all nodes -->
<purging-enable>true</purging-enable>
<cron-expression>0 50 11 * * ?</cron-expression>
<!-- Tables that need include to purging. Use regex expression to specify the table name that need include to purging.-->
<purge-include-tables>
<table>.*</table>
<!--<table>.*jmx.*</table>-->
</purge-include-tables>
<!-- All records that insert before the specified retention time will be eligible to purge -->
<data-retention-days>365</data-retention-days>
</analytics-data-purging>
</analytics-dataservice-configuration>
作为检查DAS碳门户ORG_ *表的结果,数据在清除时间后被删除。 但是剩下两个数据库(WSO2_ANALYTICS_EVENT_STORE_DB,WSO2_ANALYTICS_PROCESSED_DATA_STORE_DB)。
问题是:
正在清除配置封面ORG_ *表吗? 或者设置错了?
答案 0 :(得分:-1)
请您澄清一下您的意思
但是剩下两个数据库(WSO2_ANALYTICS_EVENT_STORE_DB,WSO2_ANALYTICS_PROCESSED_DATA_STORE_DB)。
你的意思是你仍然可以在数据库中看到表格吗?如果是,那就是设计。 DAS数据清除仅删除早于指定时间的记录,它不会删除表本身。