Hi, we've been looking at all the smolt outages recently, and after looking into it a bit, we'd like to try converting the host table in the smolt database to InnoDB so that we will get row level locking.
This is a very low impact change, and when we tested in staging, it caused smolt to stop accepting new submissions for about 20 minutes (smoltSendProfile will simply time out during that period). If we run into any issues, we can easily revert back to MyISAM (and doing so took <5 minutes on staging).
Can I get two +1s for this?
Thanks, Ricky
On Wed, Aug 12, 2009 at 5:46 AM, Ricky Zhouricky@fedoraproject.org wrote:
Hi, we've been looking at all the smolt outages recently, and after looking into it a bit, we'd like to try converting the host table in the smolt database to InnoDB so that we will get row level locking.
This is a very low impact change, and when we tested in staging, it caused smolt to stop accepting new submissions for about 20 minutes (smoltSendProfile will simply time out during that period). If we run into any issues, we can easily revert back to MyISAM (and doing so took <5 minutes on staging).
Can I get two +1s for this?
+1
On Wed, 12 Aug 2009, Xavier Lamien wrote:
On Wed, Aug 12, 2009 at 5:46 AM, Ricky Zhouricky@fedoraproject.org wrote:
Hi, we've been looking at all the smolt outages recently, and after looking into it a bit, we'd like to try converting the host table in the smolt database to InnoDB so that we will get row level locking.
This is a very low impact change, and when we tested in staging, it caused smolt to stop accepting new submissions for about 20 minutes (smoltSendProfile will simply time out during that period). If we run into any issues, we can easily revert back to MyISAM (and doing so took <5 minutes on staging).
Can I get two +1s for this?
+1
+1 this is something we'e been working on for a while
-Mike
infrastructure@lists.fedoraproject.org
-
Mike McGrath -
Ricky Zhou -
Xavier Lamien