Dsync woocommerce1/29/2024 Username priority fast sync full sync success sync failed test100 none 02 : 03 : 52 02 : 08 : 52 02 : 03 : 52 - test1 none 00 : 00 : 01 00 : 43 : 33 03 : 20 : 46 y test2 none 02 : 03 : 51 02 : 03 : 51 02 : 03 : 51 -įast sync: How long time ago the last “fast sync” (non-full sync)Īttempt was performed. The username patternĬan contain ‘*’ and ‘?’ wildcards. The per-user replication status can be shown withĭoveadm replicator status. Total number of known users: Number of users that replicator knows Waiting ‘failed’ requests: Number of users whose last replicationĪttempt failed, and we’re now waiting for the retry interval (5 mins) Have any replication pending, but who are currently waiting for a Queued ‘full resync’ requests: Number of users who don’t specifically Retried as soon as higher priority users’ replication has finished. Pending and where the last sync attempt failed. Queued ‘failed’ requests: Number of users who have a replication Queued ‘low’ requests: This priority is used for everything else Queued ‘high’ requests: This priority is used only for mail saves if Replication_sync_timeout setting is used. Queued ‘sync’ requests: This priority is used only for mail saves if The same user can only be in one (or none) of these The first 3 fields describe users who have a replication pending with a Queued 'sync' requests 0 Queued 'high' requests 0 Queued 'low' requests 0 Queued 'failed' requests 0 Queued 'full resync' requests 90 Waiting 'failed' requests 10 Total number of known users 100
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |