Ticket #383 (closed defect: fixed)

Opened 2 years ago

Last modified 1 year ago

browse is showing incorrect results

Reported by: russ Assigned to: russ
Priority: critical Milestone:
Component: ambra Version: 0.7
Keywords: Cc:
Blocking: Blocked By:

Description

howdy!

chris noticed this morning that browse by date on stack two was only showing 3 results for the last week.

stack one was showing 15.

i suspected either a plosone/caching issue or a lucene sync issue.

i restarted plosone on stack 2 and it showed 19 articles in the past week.

i restarted plosone on stack 1 and it showed 19 articles in the past week.

so BOTH plosone servers were reporting incorrect results. which is lame. at least it's not a lucene issue.

i'm beginning to get the feeling that browse is flaky. please take a look at this once 0.7 is out the door.

thanks!

http://www.plosone.org/article/browse.action?field=date

Dependency Graph

Change History

06/14/07 10:45:26 changed by ebrown

Hi Russ, Do you restart the plosone servers after ingestion?

06/15/07 16:20:57 changed by russ

no. we never restart the plosone servers unless things are borked.

06/18/07 17:13:41 changed by russ

  • version changed from 0.6 to 0.7.

this problem persists in 0.7

in fact, it looks like browse just doesn't get updated on ingested at all, and that browse is not updated until plosone restart.

i'll monitor this after update and see if we need to (ugh) restart plosone for now after each ingest.

06/20/07 13:29:28 changed by russ

  • priority changed from high to critical.

and this is still happening after yesterday's ingest.

can you tell me if browse is *supposed* to update itself on ingest?

i will start restarting the plosone service after each ingest, but i'd like some information about this.

06/20/07 13:56:26 changed by stevec

Yes, it is supposed to clear the cache and update with the new info. You do have to publish for that to happen. I haven't seen the problem on our servers, but I'll double check.

06/20/07 15:02:41 changed by stevec

Fix browse service so that it is session scoped. This may (in part) be the cause of #383. Note that this fix will not reset the user's session. If he was browsing the site and then something was published, he may not pick up that change until his session expires. This is not ideal, but at the moment, this is the safest fix for the branch. If this presents a big problem, I can also make a change to browse which will make it work as expected.

06/20/07 15:24:12 changed by stevec

[2969] and [2967] should actually take care of this issue. It should behave as expected. Don't worry about what I said in the previous post about updates not showing up in a user's session.

06/21/07 10:39:15 changed by russ

  • owner changed from stevec to russ.

great. i will test after this morning's update.

06/21/07 10:39:22 changed by russ

  • milestone changed from 0.8 to 0.7.

06/21/07 10:39:32 changed by russ

  • status changed from new to assigned.

06/21/07 11:20:52 changed by russ

  • status changed from assigned to closed.
  • resolution set to fixed.

tested and working! thanks!

07/03/07 14:46:03 changed by ebrown

See also #436

10/29/07 21:13:36 changed by

  • milestone deleted.

Milestone 0.7 deleted