You can apply these by going to the root of your Review Board package
(probably /usr/lib/python2.7/site-packages/ReviewBoard-2.5.9-py2.7.egg) and
running:
patch -p1 < *.patch
Probably should back up your package directory just in case first.
If the patches apply successfully, perform a
Sure thing.
Python: 2.7.5.
I used easy_install to install RB.
On Monday, May 1, 2017 at 4:28:14 PM UTC-5, Christian Hammond wrote:
>
> Actually, rather than the Elasticsearch patch, I'd like you to try a
> couple patches to the search indexing code. Turns out it was more
> inefficient than
Actually, rather than the Elasticsearch patch, I'd like you to try a couple
patches to the search indexing code. Turns out it was more inefficient than
I had thought. Alternatively, I could send you a build. Just need to know
the Python version and whether you used easy_install or pip to install
Thanks for the quick reply Christian!
I would like the info on configuring Elasticsearch if you don't mind.
--DK
On Monday, May 1, 2017 at 3:12:06 PM UTC-5, Christian Hammond wrote:
>
> Hi Daniel,
>
> I believe this happens because unlike review requests, we have no way of
> determining with
Hi Daniel,
I believe this happens because unlike review requests, we have no way of
determining with the search indexing stuff we use if a user's information
is "new" to the index. Basically, we have no "last updated" for the users.
I do see an area in the search index for users that isn't as
I have a fresh 2.5.9 install with a db taken from a backup of another 2.5.9
install (basically a backup of my production instance).
On the production instance, I am experiencing 100% cpu usage every time the
update_index cron job runs causing my users to complain about
responsiveness of the
