[wp-trac] [WordPress Trac] #19263: Possible Akismet concurrency issue in comment-check

WordPress Trac wp-trac at lists.automattic.com
Fri Nov 18 01:08:15 UTC 2011


#19263: Possible Akismet concurrency issue in comment-check
--------------------------+----------------------
 Reporter:  archon810     |       Owner:
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  Cron          |     Version:
 Severity:  normal        |  Resolution:  invalid
 Keywords:                |
--------------------------+----------------------
Changes (by nacin):

 * status:  new => closed
 * resolution:   => invalid
 * milestone:  Awaiting Review =>


Old description:

> I've been working at narrowing down high load on a busy server and
> noticed what seems to be a bunch of concurrency problems.
>
> The main one is wp-cron running in multiple HTTP threads and destroying
> the server (see #17462), so this may be related if what you see below is
> a result of wp-cron tasks.
>
> However, if it's not, then akismet seems to be suffering from the same
> issue.
>
> I'm using dd32's http://wordpress.org/extend/plugins/core-control to log
> these requests. Notice a lot of them on the exact same second, which
> points at a concurrency issue.
>
> {{{
>         POST http://102157caa02c.rest.akismet.com/1.1/comment-check
> 200ok   0s      2011-11-16 10:06:45
>         POST http://102157caa02c.rest.akismet.com/1.1/comment-check
> 200ok   0s      2011-11-16 10:06:24
>         POST http://102157caa02c.rest.akismet.com/1.1/comment-check
> 200ok   0s      2011-11-16 10:04:39
>         POST http://102157caa02c.rest.akismet.com/1.1/comment-check
> 200ok   0s      2011-11-16 10:02:18
>         POST http://102157caa02c.rest.akismet.com/1.1/comment-check
> 200ok   0s      2011-11-16 10:01:01
>         POST http://102157caa02c.rest.akismet.com/1.1/comment-check
> 200ok   0s      2011-11-16 10:00:07
>         POST http://102157caa02c.rest.akismet.com/1.1/comment-check
> 200ok   0s      2011-11-16 09:59:38
>         POST http://102157caa02c.rest.akismet.com/1.1/comment-check
> 200ok   0s      2011-11-16 09:59:26
>         POST http://102157caa02c.rest.akismet.com/1.1/comment-check
> 200ok   0s      2011-11-16 09:59:26
>         POST http://102157caa02c.rest.akismet.com/1.1/comment-check
> 200ok   0s      2011-11-16 09:59:26
>         POST http://102157caa02c.rest.akismet.com/1.1/comment-check
> 200ok   0s      2011-11-16 09:59:26
>         POST http://102157caa02c.rest.akismet.com/1.1/comment-check
> 200ok   0s      2011-11-16 09:59:26
>         POST http://102157caa02c.rest.akismet.com/1.1/comment-check
> 200ok   0s      2011-11-16 09:59:26
>         POST http://102157caa02c.rest.akismet.com/1.1/comment-check
> 200ok   0s      2011-11-16 09:59:26
>         POST http://102157caa02c.rest.akismet.com/1.1/comment-check
> 200ok   0s      2011-11-16 09:59:26
>         POST http://102157caa02c.rest.akismet.com/1.1/comment-check
> 200ok   0s      2011-11-16 09:59:26
>         POST http://102157caa02c.rest.akismet.com/1.1/comment-check
> 200ok   0s      2011-11-16 09:59:26
>         POST http://102157caa02c.rest.akismet.com/1.1/comment-check
> 200ok   0s      2011-11-16 09:59:26
>         POST http://102157caa02c.rest.akismet.com/1.1/comment-check
> 200ok   0s      2011-11-16 09:59:26
>         POST http://102157caa02c.rest.akismet.com/1.1/comment-check
> 200ok   0s      2011-11-16 09:59:26
>         POST http://102157caa02c.rest.akismet.com/1.1/comment-check
> 200ok   0s      2011-11-16 09:59:26
>         GET
> http://api.twitter.com/1/users/show.json?screen_name=AndroidPolice  200ok
> 0.052s  2011-11-16 09:59:24
>         POST http://102157caa02c.rest.akismet.com/1.1/comment-check
> 200ok   0s      2011-11-16 09:58:47
>         POST http://102157caa02c.rest.akismet.com/1.1/comment-check
> 200ok   0s      2011-11-16 09:58:17
>
> }}}
>
> So, are these the result of poor cron locking in <3.3 or is there a
> separate issue here altogether?

New description:

 I've been working at narrowing down high load on a busy server and noticed
 what seems to be a bunch of concurrency problems.

 The main one is wp-cron running in multiple HTTP threads and destroying
 the server (see #17462), so this may be related if what you see below is a
 result of wp-cron tasks.

 However, if it's not, then akismet seems to be suffering from the same
 issue.

 I'm using dd32's http://wordpress.org/extend/plugins/core-control to log
 these requests. Notice a lot of them on the exact same second, which
 points at a concurrency issue.

 {{{
         POST http://.rest.akismet.com/1.1/comment-check 200ok   0s
 2011-11-16 10:06:45
         POST http://.rest.akismet.com/1.1/comment-check 200ok   0s
 2011-11-16 10:06:24
         POST http://.rest.akismet.com/1.1/comment-check 200ok   0s
 2011-11-16 10:04:39
         POST http://.rest.akismet.com/1.1/comment-check 200ok   0s
 2011-11-16 10:02:18
         POST http://.rest.akismet.com/1.1/comment-check 200ok   0s
 2011-11-16 10:01:01
         POST http://.rest.akismet.com/1.1/comment-check 200ok   0s
 2011-11-16 10:00:07
         POST http://.rest.akismet.com/1.1/comment-check 200ok   0s
 2011-11-16 09:59:38
         POST http://.rest.akismet.com/1.1/comment-check 200ok   0s
 2011-11-16 09:59:26
         POST http://.rest.akismet.com/1.1/comment-check 200ok   0s
 2011-11-16 09:59:26
         POST http://.rest.akismet.com/1.1/comment-check 200ok   0s
 2011-11-16 09:59:26
         POST http://.rest.akismet.com/1.1/comment-check 200ok   0s
 2011-11-16 09:59:26
         POST http://.rest.akismet.com/1.1/comment-check 200ok   0s
 2011-11-16 09:59:26
         POST http://.rest.akismet.com/1.1/comment-check 200ok   0s
 2011-11-16 09:59:26
         POST http://.rest.akismet.com/1.1/comment-check 200ok   0s
 2011-11-16 09:59:26
         POST http://.rest.akismet.com/1.1/comment-check 200ok   0s
 2011-11-16 09:59:26
         POST http://.rest.akismet.com/1.1/comment-check 200ok   0s
 2011-11-16 09:59:26
         POST http://.rest.akismet.com/1.1/comment-check 200ok   0s
 2011-11-16 09:59:26
         POST http://.rest.akismet.com/1.1/comment-check 200ok   0s
 2011-11-16 09:59:26
         POST http://.rest.akismet.com/1.1/comment-check 200ok   0s
 2011-11-16 09:59:26
         POST http://.rest.akismet.com/1.1/comment-check 200ok   0s
 2011-11-16 09:59:26
         POST http://.rest.akismet.com/1.1/comment-check 200ok   0s
 2011-11-16 09:59:26
         GET
 http://api.twitter.com/1/users/show.json?screen_name=AndroidPolice  200ok
 0.052s  2011-11-16 09:59:24
         POST http://.rest.akismet.com/1.1/comment-check 200ok   0s
 2011-11-16 09:58:47
         POST http://.rest.akismet.com/1.1/comment-check 200ok   0s
 2011-11-16 09:58:17

 }}}

 So, are these the result of poor cron locking in <3.3 or is there a
 separate issue here altogether?

--

Comment:

 I don't know how Akismet currently handles bug reports, but you can report
 it against their tag on the support forums:
 http://wordpress.org/tags/akismet?forum_id=10.

 3.3 should be out by the end of the year; it won't be November.

 I removed your API key from the ticket. If you feel you should get that
 changed now, you should contact Akismet: https://akismet.com/contact.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/19263#comment:8>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software


More information about the wp-trac mailing list