Return-Path: 
 <users-return-35576-apmail-activemq-users-archive=activemq.apache.org@activemq.apache.org>
X-Original-To: apmail-activemq-users-archive@www.apache.org
Delivered-To: apmail-activemq-users-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 94988105AD
	for <apmail-activemq-users-archive@www.apache.org>;
 Thu,  1 Aug 2013 15:37:21 +0000 (UTC)
Received: (qmail 84572 invoked by uid 500); 1 Aug 2013 15:37:21 -0000
Delivered-To: apmail-activemq-users-archive@activemq.apache.org
Received: (qmail 83354 invoked by uid 500); 1 Aug 2013 15:37:18 -0000
Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@activemq.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@activemq.apache.org>
List-Post: <mailto:users@activemq.apache.org>
List-Id: <users.activemq.apache.org>
Reply-To: users@activemq.apache.org
Delivered-To: mailing list users@activemq.apache.org
Received: (qmail 82539 invoked by uid 99); 1 Aug 2013 15:37:17 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Aug 2013 15:37:17 +0000
X-ASF-Spam-Status: No, hits=1.5 required=5.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of paul.n.gale@gmail.com
 designates 209.85.214.170 as permitted sender)
Received: from [209.85.214.170] (HELO mail-ob0-f170.google.com)
 (209.85.214.170)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Aug 2013 15:37:10 +0000
Received: by mail-ob0-f170.google.com with SMTP id eh20so4209172obb.15
        for <users@activemq.apache.org>; Thu, 01 Aug 2013 08:36:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:from:date:message-id:subject:to:content-type;
        bh=RdTI2q7CML6O51JPSbiO5gCaWjecJfVIOxtcziPt9ew=;
        b=UTzfOyiXzEL4EUOXFEqfOGhedAKG8xfp4T2MHplwjbQ3v0OLOnGUIwIC/z8EVWoIFL
         dsHQTQeh3ih9IpHCNZXY3z6MLWG9kwEZj2DVA1x5YAfTiZcI59I0VJ11T5i/+Yrr5DHp
         HMORMlOp8cpNtO+zXFuAKkUA6CDAfdnTTn0y3Opr7bivbTMMUgbSAnBOiLwtc7XCGAeU
         vclC1N4Zkt/Li5HlFDDUTKmHIRWUENy20wc/Z6QqTdflXuI+8R5hR3npvQnaxjaXsCwO
         AReFqAlgexMR8oaFaD4lqfGwVZ8fa5Ctd+XbG0I5UI+uo0DE5FU1ZJn7Q0LiptAGeTGY
         pwMw==
X-Received: by 10.60.84.147 with SMTP id z19mr1768940oey.21.1375371409149;
 Thu, 01 Aug 2013 08:36:49 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.60.38.10 with HTTP; Thu, 1 Aug 2013 08:36:19 -0700 (PDT)
From: Paul Gale <paul.n.gale@gmail.com>
Date: Thu, 1 Aug 2013 11:36:19 -0400
Message-ID: 
 <CAJ5znhuZHVJyBW7EP+KHdXjiwXVtG91CBJ4LVsGXpA4J2pGSuQ@mail.gmail.com>
Subject: Influence of persistence adapter settings on speed of failover.
To: users@activemq.apache.org
Content-Type: multipart/alternative; boundary=089e01176a1146d37004e2e49cef
X-Virus-Checked: Checked by ClamAV on apache.org

--089e01176a1146d37004e2e49cef
Content-Type: text/plain; charset=UTF-8

Hi,

I have been experimenting with failover using the Master/Slave shared
storage strategy. I have a custom lease locker (shown in the example below)
that correctly obtains the lock within a couple of seconds of when the
other broker dies. However, depending on the value of the other settings
for the persistence adapter it can take over 2 minutes before the new
Master turns on its transport connectors.

Using these values shown below the broker takes just a few seconds to turn
on its transport connectors. The message store consisted of a dozen or so
32mb journal files:

<persistenceAdapter>
  <kahaDB directory="${activemq.data}/kahadb"
          indexCacheSize="10000"
          indexWriteBatchSize="1000"
          cleanupInterval="30000"
          checkpointInterval="5000"
          journalMaxFileLength="32m"
          journalMaxWriteBatchSize="4m"
          lockKeepAlivePeriod="2500"
          useLock="true">
    <locker>
      <m:manheim-lease-database-locker
              failIfLocked="false"
              maxAllowableDiffFromDBTime="1000"
              brokerService="#theBroker"
              lockDataSource="#mysql-ds"
              createLockTableOnStartup="true"
              lockAcquireSleepInterval="5000"
              lockTableName="activemq_lab_lock">
      </m:manheim-lease-database-locker>
    </locker>
  </kahaDB>
</persistenceAdapter>

However, if I set the values as shown below it takes over 2 minutes for the
master broker to turn on its transport connectors. These adapter values
were chosen based on one of the 'performance examples' that ships with
ActiveMQ:

<persistenceAdapter>
  <kahaDB directory="${activemq.data}/kahadb"
          indexCacheSize="100000"
          indexWriteBatchSize="100000"
          cleanupInterval="300000"
          checkpointInterval="50000"
          journalMaxFileLength="1g"
          journalMaxWriteBatchSize="62k"
          lockKeepAlivePeriod="2500"
          useLock="true">
    <locker>
      <m:manheim-lease-database-locker
              failIfLocked="false"
              maxAllowableDiffFromDBTime="1000"
              brokerService="#theBroker"
              lockDataSource="#mysql-ds"
              createLockTableOnStartup="true"
              lockAcquireSleepInterval="5000"
              lockTableName="activemq_lab_lock">
      </m:manheim-lease-database-locker>
    </locker>
  </kahaDB>
</persistenceAdapter>

Note that the message store resides on an NFS v3 mount.

Thanks,
Paul

--089e01176a1146d37004e2e49cef--