Hi Martin :

This is another client reported issue on app.islg. Please add it to unplanned/critical.

Disputes Dispute Document filter and search field error (21-Jan-22).mp4 12.9 MB • Download

Thanks,

Paul

Hi Harsh ,

I have added task https://dev.azure.com/tologix/ISLGRebuild/_workitems/edit/1422 to track this issue.

Note that this issue only occurs on Production. It is working as expected on Staging.

Thanks,
-Martin

Hi Harsh and Martin :

A client is experiencing an issue below. It is a further disruption from my previous video above.

Disputes Dispute Document filter and search field error 2 (25-Jan-22).mp4 1.62 MB • Download

Thanks,

Paul

Hi Radomir ,

Could you please look into this issue ?

Dispute Document Indexing on production environment is not creating successfully from last 2 days. Also, It is taking so much time to create Index for Dispute Document.

Before some days It was taking only half n hour.

Databse Name : ISLGRebuildProduction
Indexer Project : E:\DevISLGRebuildProductionDBIndexer
Indexing Path : E:\DevISLGRebuildProductionIndexDailyGenerate

indexer-config-dispute-docs.json 495 Bytes • Download

Cc : Martin   Paul   Rob  

Hi Rob and Radomir ,

This is a serious issue for us and it is impacting our subscribers. Until this is resolved, we will need to manually monitor the indexing job.

Radomir : could the increase in time to index Dispute Documents (from 30 minutes to >5 hours) be related to the latest changes made a few weeks ago?

Thanks,
-Martin

Yes, this was caused by recent changes. I fixed it and indexing now took about an hour. Not sure if it was really half an hour before. It can probably be further speedup at least disabling the debug logging level (it generated a file >1GB for me).

Harsh you can get an update from:
https://1drv.ms/u/s!AugzRBG6eTFwjv1fCmSOyXYloTFPaQ?e=AE4ZHd

Hi Radomir ,

How we will disable the debug logging level ? Where we need to do this ?

Cc : Martin  

Harsh in the TologixDBIndexer.exe.conf change the root level to INFO.

image.png 2.75 KB • Download

 Marked resolved under DevOps 1422

Hi Martin :

This is a regression issue of below that came back today identified by Irit .

image.png 225 KB • Download

Please address it as soon as possible as an unplanned/critical item.

Disputes Dispute Document filter and search field error 3 (15-Jun-22).mp4 9.92 MB • Download

Thanks,

Paul

Hi Harsh ,

Please make this your top priority on Thursday.
Are we still having issues with dtSearch? Let us know what you find out.

I have created DevOps task https://dev.azure.com/tologix/ISLGRebuild/_workitems/edit/1988 for this.

Thanks,
-Martin

Hi Martin , Harsh Radomir , Can you please confirm that the search you are showing in the video is a dtSearch query and not an SQL query. I can't see the status bar sufficiently to determine.  Thanks.

Hi Paul ,

This issue occurred yesterday due to failed to generate Dtsearch Indexes. Today The indexing generated perfectly and it is working fine.

We will make task in next sprint to automated we get the notification via Email if the indexes will not generate properly.

Radomir   and Rob , Do you have any idea for how will get notification if indexes are not generated ?

Cc : Martin  

Hi Paul ,

I have created DevOps https://dev.azure.com/tologix/ISLGRebuild/_workitems/edit/1990 to track the task Harsh describes above.

Please put this on top of the backlog so we can pick it up in the next sprint.

Thanks,
-Martin

Installed on production on August 10th.