On 09/20/2012 06:10 AM, Russell Jackson wrote:
I recently merged upstream master into my local installation.
Apparently the sharding default was changed to be disabled which was
causing a rather confusing problem
with push processing. I was getting ActiveMessagingAbort exceptions
from the push processor on every push to new repositories created and
only to new repositories. After enabling sharding again and recreating
the repositories, the problem went away.
The symptoms were identical to those in this posting:
https://groups.google.com/forum/?fromgroups=#!topic/gitorious/c6jZdl89QCg
<https://groups.google.com/forum/?fromgroups=#%21topic/gitorious/c6jZdl89QCg>
I also found that all traces of this setting were removed from the
example gitorious.yml config for some reason. I only found it by
looking through the commit log.
--
To post to this group, send email to gitorious@googlegroups.com
To unsubscribe from this group, send email to
gitorious+unsubscr...@googlegroups.com
Hi Russel,
first off, I've ensured that the doc and example sharding settings is
back in the sample gitorious.yml file. Seems to have been overwritten by
a merge a while back. Thanks for the catch.
Second: having trouble reproducing your issue. I fired up a cleanroom
Gitorious VM, enabled sharding, created projects/repos, pushed code,
turned off sharding, pushed more code without issue. Also tried the
reverse: created project/repo while not sharded, pushed code, re-enabled
sharding, pushed again. None of these scenarios caused any exceptions in
either the /log/message_processing.log or /log/production.log.
Is your scenario different from what I tested above? What am I missing here?
--
best regards,
Thomas Kjeldahl Nilsson
http://gitorious.com
--
To post to this group, send email to gitorious@googlegroups.com
To unsubscribe from this group, send email to
gitorious+unsubscr...@googlegroups.com
