Mailing-List: contact issues-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Thu, 5 Jan 2017 14:59:58 +0000 (UTC)
From: "Timothy Bish (JIRA)" <jira@apache.org>
To: issues@activemq.apache.org
Message-ID: <JIRA.13032227.1483615545000.650851.1483628398537@Atlassian.JIRA>
In-Reply-To: <JIRA.13032227.1483615545000@Atlassian.JIRA>
References: <JIRA.13032227.1483615545000@Atlassian.JIRA> <JIRA.13032227.1483615545796@arcas>
Subject: [jira] [Closed] (AMQ-6553) ReplicatedLevelDB with Zookeeper :
 ActiveMQ Broker Stop when leader stop
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Thu, 05 Jan 2017 15:00:00 -0000


     [ https://issues.apache.org/jira/browse/AMQ-6553?page=3Dcom.atlassian.=
jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Bish closed AMQ-6553.
-----------------------------
    Resolution: Invalid

Questions on usage and configuration belong on the users mailing list.

LevelDB is not longer supported, see http://activemq.apache.org/leveldb-sto=
re.html

> ReplicatedLevelDB with Zookeeper : ActiveMQ Broker Stop when leader stop
> ------------------------------------------------------------------------
>
>                 Key: AMQ-6553
>                 URL: https://issues.apache.org/jira/browse/AMQ-6553
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker, OSGi/Karaf, Transport
>    Affects Versions: 5.12.1
>         Environment: Servicemix 5.5.2
> Activemq-osgi 5.12.1
>            Reporter: Man=C3=A7aux Pierre-Alexandre
>
> hello,
> I m using replicatedLevelDB to use zookeeper and clustering activemq brok=
er.
> all work fine when all is started.
> here is my configuration
> 3 servicemix=20
> each servicemix have a bundle zookeeper 3.4.6 and a bundle zookeeper-serv=
er (my code to start zookeeper server)
> each servicemix have is own activemq broker
> Firslty, i start all my zookeeper-server bundle, and all work fine, i do=
=20
> echo stat | nc localhost 2181
> echo stat | nc localhost 2182
> echo stat | nc localhost 2183
> and i have 1 Leader and 2 Followers.
> After i configure each activemq broker with :
> <persistenceAdapter>
>         <replicatedLevelDB
>             directory=3D"${data}"
>             replicas=3D"3"
>             bind=3D"tcp://0.0.0.0:61622"
>             zkAddress=3D"localhost:2181,localhost:2182,localhost:2183"
>             zkPassword=3D"password"
>             zkPath=3D"/activemq/leveldb-stores"
>             hostname=3D"[I PUT MY IP BUT HIDE IN THIS JIRA]"
>             />
>         </persistenceAdapter>
> the only thing that change is the bind parameter with different port.
> I start all my broker and all work fine, if i launch the karaf command bs=
tat on my servicemix, i can see my queue/topic on 1 broker, and the 2 other=
s just show me=20
> smx@zookeeper2> bstat
> Uptime =3D 46 minutes
> if i stop the master broker, zookeeper elect another one to be the master=
 and it works.
> but if i stop my zookeepr Leader, master broker is stop and another one i=
s up, but when i say broker is stop, bstat don't show me anything anymore o=
n this instance.
> so i have loose 1 broker and it can't be elected anymore.
> here is the log i see:=20
> 2017-01-05 11:22:46,415 | WARN  | spatch-DEFAULT-2 | MasterLevelDBStore  =
             | 96 - org.apache.activemq.activemq-osgi - 5.12.1 | Unexpected=
 session error: java.io.IOException: Connection reset by peer
> 2017-01-05 11:22:46,429 | ERROR | meSize=3D104857600 | TransportConnector=
               | 96 - org.apache.activemq.activemq-osgi - 5.12.1 | Could no=
t accept connection : java.lang.InterruptedException
> 2017-01-05 11:22:46,461 | WARN  | spatch-DEFAULT-3 | MasterLevelDBStore  =
             | 96 - org.apache.activemq.activemq-osgi - 5.12.1 | Unexpected=
 session error: java.io.IOException: Connection reset by peer
> my question is :
> why, when i stop the zookeeper leader, the master broker is killed?
> why, in this case, we don't wait a little that another zookeeper become t=
he leader and don't stop the master broker, but just reinitialize the conne=
ction to the new zookeeper master?
> or=20
> when, in this case, if its necessary to stop the broker and let zookeeper=
 reelect a new one, why the broker is kill and cannot be reelect by zookeep=
er anymore? does it possible to let it up to be reelected?
> possibly i miss something in the configuration that can prevent this prob=
lem, but if not, how can i solve my problem?
> thanks


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)