Large table elementdata partitions found / General DMS health best practices

Solved1.16K viewsCassandra DataMiner Health DMS
5
0 Comments

Hi all, my DMS is running slowly and I've noticed that information events are delayed by over 2 hours behind real time. Rather than just restart, (the server had a restart 6 weeks ago) I'd like to know what's causing the issue. I've noted the following from Agents/BPA messages... (Cassandra DB Size) 'Large partitions detected for table elementdata Partitions: [partitionkey: 31148:26102 - size: 131.817MiB] Large partitions detected for table infotrace Partitions: [partitionkey: Unknown (reported by Nodetool) - size: 765 MiB]'   This makes sense to me as the Element does have very large tables and the data is changing constantly. I've since deleted the Element and re-run the Cassandra BPA tool in system center, the message still exists.

Is there anything I should be checking apart from this? Are there any tools in DM to clean or refresh old files to keep the agent in better condition? Are there any files I can manually delete to help? Where can I check how much alarm, trend and parameter data is stored? Maybe this could be reduced to help? Any other best practices?

Thanks!

Ross

Alexander Gorbunov [SLC] [DevOps Advocate] Answered question 23rd May 2023

2 Answers

1
978 0 Comments

Hi Ross,

I'm replying somewhat late to this question, but I would like to clarify that the symptoms you observed - information events arriving up to two hours late - are not likely to be caused by the DB size BPA warnings you mentioned. From experience, even the infotrace partition of 3 GB has little, if any, impact on DMA performance.

The issue with delayed information events is not something we come across often. If it's still present, it would be best to report this issue to Techsupport for a proper investigation.

As for your additional questions:

Alexander Gorbunov [SLC] [DevOps Advocate] Answered question 23rd May 2023
You are viewing 1 out of 2 answers, click here to view all answers.