I’m seeing a warning in Pulse that There are pending Elastic Transactions. When I look in the Application Logs, I see the following repeating every 30 seconds. The chore / process history is not being updated, which I assume relates to the errors. What could be the cause of the errors and what needs to be done to fix it?
There was 23 GB of 200GB available on the drive Pulse is installed to. More space was freed up yesterday in case it was a disk space issue and there is now 60GB free, but the errors still keep repeating and the chore / process history is still not being updated.
Pulse version 6.0.5.
The following errors repeating in Pulse.
2023-02-08 18:07:26 INFO ElasticJob processing 1 backup files
2023-02-08 18:07:26 ERROR ElasticBatchTransaction Errors when performing Batch save to Elastic, activate debug mode for more details
2023-02-08 18:07:26 WARN ElasticBatchTransaction F:\Program Files\Pulse for TM1\temp\elastic\BulkServerStateFullElastic$BulkTM1TopItemElastic_BulkFileindexation_1675840017009.json processed with errors
2023-02-08 18:07:26 WARN ElasticBatchTransaction There were transactions that did not succeed, saving them in the temp folder
2023-02-08 18:07:27 FATAL ElasticJob Errors when processing Backup files, the job cannot continue
com.cubewise.elastic.api.ElasticException: Pulse could not commit all the pending documents, check with your Elastic Administrator
at com.cubewise.P.a(SourceFile:2349)
at com.cubewise.P.execute(SourceFile:191)
at org.quartz.core.JobRunShell.run(JobRunShell.java:207)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:560)
2023-02-08 18:07:31 WARN SystemStatusJob There are pending documents that were not indexed in Elastic, check the elastic logs for more details
What happened is that as there was not enough free disk space on the server, Pulse stopped sending data to Pulse Elasticsearch. Even after adding more free space on the server, Pulse is not able to recover this data. This is a known issue in Pulse v6.0.x.
Pulse v6.0.5 is 4 releases behind the current release v6.1.3. We added many optimizations to the Pulse Elasticsearch feature. One of them is to better handle these types of situations.
I highly recommend you to upgrade Pulse asap.
If you can’t upgrade, you can try the following steps:
stop the Pulse Services
clear C:\Program Files\Pulse for TM1\temp\elastic\ folder.
I tried the 3 steps, but it hasn’t fixed the issue. The errors are different, and chore / process history is still not being updated.
2023-02-10 17:57:50 WARN SystemStatusJob There are pending documents that were not indexed in Elastic, check the elastic logs for more details
2023-02-10 17:58:14 INFO ElasticJob processing 5 backup files
2023-02-10 17:58:14 ERROR ElasticBatchTransaction Errors when performing Batch save to Elastic, activate debug mode for more details
2023-02-10 17:58:14 WARN ElasticBatchTransaction F:\Program Files\Pulse for TM1\temp\elastic\BulkServerStateFullElastic$BulkDriveElastic_BulkFileindexation_1676012265051.json processed with errors
2023-02-10 17:58:14 WARN ElasticBatchTransaction There were transactions that did not succeed, saving them in the temp folder
2023-02-10 17:58:15 ERROR ElasticBatchTransaction Errors when performing Batch save to Elastic, activate debug mode for more details
2023-02-10 17:58:15 WARN ElasticBatchTransaction F:\Program Files\Pulse for TM1\temp\elastic\BulkServerStateFullElastic$BulkServiceStateElastic_BulkFileindexation_1676012265567.json processed with errors
2023-02-10 17:58:15 WARN ElasticBatchTransaction There were transactions that did not succeed, saving them in the temp folder
2023-02-10 17:58:15 ERROR ElasticBatchTransaction Errors when performing Batch save to Elastic, activate debug mode for more details
2023-02-10 17:58:15 WARN ElasticBatchTransaction F:\Program Files\Pulse for TM1\temp\elastic\BulkServerStateFullElastic$BulkTM1TopItemElastic_BulkFileindexation_1676012266105.json processed with errors
2023-02-10 17:58:15 WARN ElasticBatchTransaction There were transactions that did not succeed, saving them in the temp folder
2023-02-10 17:58:16 ERROR ElasticBatchTransaction Errors when performing Batch save to Elastic, activate debug mode for more details
2023-02-10 17:58:16 WARN ElasticBatchTransaction F:\Program Files\Pulse for TM1\temp\elastic\BulkServerStateFullElastic$BulkTM1Top_BulkFileindexation_1676012266648.json processed with errors
2023-02-10 17:58:16 WARN ElasticBatchTransaction There were transactions that did not succeed, saving them in the temp folder
2023-02-10 17:58:16 ERROR ElasticBatchTransaction Errors when performing Batch save to Elastic, activate debug mode for more details
2023-02-10 17:58:16 WARN ElasticBatchTransaction F:\Program Files\Pulse for TM1\temp\elastic\BulkServerStateFullElastic_BulkFileindexation_1676012267163.json processed with errors
2023-02-10 17:58:16 WARN ElasticBatchTransaction There were transactions that did not succeed, saving them in the temp folder
2023-02-10 17:58:17 FATAL ElasticJob Errors when processing Backup files, the job cannot continue
com.cubewise.elastic.api.ElasticException: Pulse could not commit all the pending documents, check with your Elastic Administrator
at com.cubewise.P.a(SourceFile:2349)
at com.cubewise.P.execute(SourceFile:191)
at org.quartz.core.JobRunShell.run(JobRunShell.java:207)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:560)