• Hey Guys!

    I installed this plugin on our production site yesterday. It is a multi-site with 2 sites. A public facing site and a “membership” side.

    I started by running the “Index MySQL for WordPress” companion plugin on both the public and members sites.

    When I ran the first user index build with this plugin everything worked good on the “Production” site. It took about an hour and a half, but all ~330k of our users were indexed.

    The notice properly went away after I watched it work it’s way up from 0 to 100.

    As far as I can tell lasts nights index rebuild worked without an issue as well.

    HOWEVER, since I installed the plugin the “members” side of the site has shown this notice on the backend:

    “Background user index building in progress:?0% complete. You may use your site normally during index building.”

    That 0% has not moved, and as far as I can tell from NewRelic there is no indexing process running.

    The plugin says it’s multisite compatible, so I’m wondering if that notice is a false positive? Is there anything else we need to do to run the user indexing on the members side, did it run while the public facing sites indexing run?

    Thanks so much!

    -Simon

Viewing 1 replies (of 1 total)
  • Plugin Author OllieJones

    (@olliejones)

    Thanks for letting me know about this.

    I did test the plugin, extensively, on a multisite installation with 100K fake users distributed among various subsites.

    The plugin uses transients to keep track of its reindexing operations. You might try going to its settings page (Users -> Index for Speed) and choose Immediately, then daily.

    If that doesn’t work, you can try deactivating and reactivating the plugin. That wipes out the transients and starts over on the indexing.

    It does the indexing “in the background”, meaning with a sequence of WP_Cron jobs running immediately. Each WP_Cron job handle 5000 users.

    If you leave a dashboard page visible in the subsite you are indexing, the dashboard’s heartbeat feature kicks off a new cron every 15 seconds or so. That works around a disabled automatic WP_Cron.

    Please let me know whether this solves your problem.

Viewing 1 replies (of 1 total)
  • The topic ‘Multisite “Stalled Indexing” Question’ is closed to new replies.