Highlighted

Failed synchronizing Error in Standby server

seemak19887037

23-09-2019

We have configured standby server in which data is copying from primary to standby but each and every day we are getting error related to some inconsistency:-

java.lang.IllegalStateException: Unable to load remote blob d171b4854087624cd182b6a7c6d130218d447c138d78dae37fd7d004ab32011c#249045 at /root/oak:index/damAssetLucene/:suggest-data/_6fd_Lucene45_0.dvd/#jcr:data

java.lang.IllegalStateException: Unable to load remote blob d171b4854087624cd182b6a7c6d130218d447c138d78dae37fd7d004ab32011c#249045 at /root/oak:index/damAssetLucene/:suggest-data/_6fd_Lucene45_0.dvd/#jcr:data

java.lang.IllegalStateException: Unable to load remote blob 10b8935b7b917ff615ce95da2a0da998280ce795052ba030a48d27a52792258d#249045 at /root/oak:index/damAssetLucene/:suggest-data/_6fe_Lucene45_0.dvd/#jcr:data

java.lang.IllegalStateException: Unable to load remote blob 5b073ecf3ee27735351bd4cef9095cb139b44822b5903e1d9d449484bb91f0aa#249045 at /root/oak:index/damAssetLucene/:suggest-data/_6ff_Lucene45_0.dvd/#jcr:data

java.lang.IllegalStateException: Unable to load remote blob a6d98ffee9a17bc9cd66ea9cf3224b4236471c46c25e97259a28f1e8134b8eac#145830 at /root/oak:index/damAssetLucene/:suggest-data/_6fh_Lucene41_0.doc/#jcr:data

java.lang.IllegalStateException: Unable to load remote blob a6d98ffee9a17bc9cd66ea9cf3224b4236471c46c25e97259a28f1e8134b8eac#145830 at /root/oak:index/damAssetLucene/:suggest-data/_6fh_Lucene41_0.doc/#jcr:data

java.lang.IllegalStateException: Unable to load remote blob a6d98ffee9a17bc9cd66ea9cf3224b4236471c46c25e97259a28f1e8134b8eac#145830 at /root/oak:index/damAssetLucene/:suggest-data/_6fh_Lucene41_0.doc/#jcr:data

Can anyone help here to resolve these errors?

We are using AEM 6.3 instance.AEM - Questions​ !

Replies

Highlighted

berliant

Employee

23-09-2019

"Unable to load remote blob" is a known issue. The thing that is causing the sync to fail almost every time is a timeout error. The journal file gets updated after every sync cycle whose duration depends on the no. of changes and the volume of the repository. As a possible solution, try to increase the Timeout in the StandbyStore Service Configuration [1]

[1] How to Run AEM with TarMK Cold Standby

Highlighted

SonDang

Employee

24-09-2019

Have you thought about using shared datastore between the primary and standby to reduce the overhead associated with migrating binary files?