Page MenuHomePhabricator

When queueing search index tasks, include the "objectPHID" in the task metadata
ClosedPublic

Authored by epriestley on Jun 22 2018, 12:40 PM.
Tags
None
Referenced Files
F18790271: D19502.id46633.diff
Wed, Oct 15, 1:22 PM
F18739176: D19502.diff
Wed, Oct 1, 8:14 PM
F18710126: D19502.diff
Mon, Sep 29, 1:28 AM
F18681244: D19502.id.diff
Fri, Sep 26, 3:59 AM
F18509680: D19502.id.diff
Sep 5 2025, 3:32 AM
F18502948: D19502.diff
Sep 4 2025, 10:46 PM
F18457790: D19502.id46633.diff
Sep 1 2025, 1:04 PM
F18371743: D19502.diff
Aug 28 2025, 5:37 AM
Subscribers
None

Details

Summary

Ref T13151. See PHI719. One minor hiccup in debugging the issue (which ended up being "revision has 100K comments") was that the SearchWorker did not show which object it was indexing.

Add 'objectPHID' to the queue call so you can see which object is affected from the web UI.

Test Plan
  • Stopped daemons.
  • Used bin/search index D123 --background to queue a search task.
  • Viewed task details in web UI from /daemon/.
    • Before change: no indication of which object was being indexed.
    • After change: page helpfully shows that the task is indexing D123.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable