Hi Gihan,
IMHO the recommended behaviour of the server needs to be as default
configuration, and since our recommendation is configure purging to have
smooth operation without getting accumulated with high amount of data in
the data store. Therefore can we have some reasonable configuration for
Hi Nirmal,
Thanks for sharing the necessary details. It's due to the data purging
configuration has been enabled in the analytics-conf.xml which uses the
task internally. can you please try to comment the analytics purging
configuration from the repository/conf/analytics/analytics-conf.xml and
Hi nirmal,
DAS features such as scripts scheduling, purging,etc are used to submit the
jobs (only spark queries) to external spark cluster, rather those DAS
features jars doesn't need to exists within the external spark cluster
instance. For example, if we consider spark script scheduled
Hi Nirmal,
When the purging disabled, if there is already registered purging task then
it'll be deleted, and therefore the it's anyhow required to access the task
service if it's enabled/disabled.
But we can check the existence of task service, and do the analytics
purging related operation if
Hi Sinthuja,
Thanks for the explanation. I think I should have used DAL instead of DAS.
Yes, so what I talking here is about the DAL features. Exact error is [1]
and reason for this is TaskService being null. Can you please check?
[1]
15/06/28 11:54:51 INFO MemoryStore: Block broadcast_0 stored
That worked Sinthuja! Thanks. However, is it possible to disable the Task
Service initialization if the purging is disabled (which is the default
behaviour)?
analytics-data-purging
purging-enablefalse/purging-enable
purge-nodetrue/purge-node
cron-expression0 0 0 * *
Hi Sinthuja,
Yes, by default data purging is disabled. It is a dev ops decision to
enable or disable the purging task and come-up with suitable input like
retention period, purge enabled tables etc.
Regards,
Gihan
On Mon, Jun 29, 2015 at 2:38 PM, Sinthuja Ragendran sinth...@wso2.com
wrote:
Hi
