Hi Tom,
Please correct me if am wrong in understanding the below statement.
The CheckedFuture will produce a derived TransactionCommitFailedException
indicating there's no leader or it timed out. You have to wait for the
CheckedFuture to be completed one way or another. It may take some number
also, there are script(s) packaged with the distribution that should be useful.
The one-click
3node cluster setup that Alexis pointed you to consumes those as well, iirc.
http://docs.opendaylight.org/en/latest/getting-started-guide/common-features/clustering.html?highlight=clustering#clustering-s
2017-02-22 6:25 GMT-05:00 bjb :
> Hello All:
>
> I see the steps to deploy a cluster in http://docs.opendaylight.
> org/en/latest/getting-started-guide/common-features/
> clustering.html?highlight=clustering
>
> I need to modify *.conf(akka.conf, modules.conf, module-shards.conf)
> on each
Daexim project worth being look at when we talk about backup/restore:
https://wiki.opendaylight.org/view/Daexim:Main
Related video showcasing some of its capabilities:
https://www.youtube.com/watch?v=fCWuuS-_xy4&feature=youtu.be
HTH,
Alexis
2017-02-21 9:56 GMT-05:00 Tom Pantelis :
>
>
> On Tue,
On Wed, Feb 22, 2017 at 1:36 PM, Satish Dutt wrote:
> Hi All,
>
>
>
> We have a 3-node clustered deployment.
>
>
>
> *Code extract : *
>
>
>
> WriteTransaction writeTxn = dataBroker.newWriteOnlyTransaction();
>
> writeTxn.put()
>
> CheckedFuture<> checkedFuture = writeTxn.submit()
>
>
>
>
>
> *Sc
Hi,
I have created two WriteTransactions from a TransactionChain instance. If I
block using the checkGet() on checkedFuture after submit on the first
transaction, will there be any impacts on the other transaction apart from the
performance deterioration ?
BindingTransactionChain bindingTransa
Hi All,
We have a 3-node clustered deployment.
Code extract :
WriteTransaction writeTxn = dataBroker.newWriteOnlyTransaction();
writeTxn.put()
CheckedFuture<> checkedFuture = writeTxn.submit()
Scenario :
1) Three nodes in the setup N1, N2, N3
2) N3 is the shard leader.
3) All RPC requests fro
The future is completed after the transaction has been replicated to a
majority of the followers and committed by the leader. If the transaction
was submitted on the leader node then a subsequent read will return the
data however this isn't guaranteed on a follower b/c the transaction may
not have
Hi All,
We write a bridge information in config DS and reading the same in next few
lines of code. (used 3 node cluster setup).
write operation is performed via
org.opendaylight.netvirt.utils.mdsal.utils.MdsalUtils::put call and read is
performed via
MdsalUtils::read call.
Observed that in Md
Hi All,
We write a bridge information in config DS and reading the same in next few
lines of code. (used 3 node cluster setup).
write operation is performed via
org.opendaylight.netvirt.utils.mdsal.utils.MdsalUtils::put call and read is
performed via
MdsalUtils::read call.
Observed that in Md
On 02/22/2017 11:51 AM, Lori Jakab wrote:
>
> org.opendaylight.controller.blueprint/0.6.0.SNAPSHOT: missing
> requirement [org.opendaylight.controller.blueprint/0.6.0.SNAPSHOT]
> osgi.wiring.package;
> filter:="(&(osgi.wiring.package=org.apache.aries.quiesce.manager)(version>=1.0.0)(!(version>=2
Hello All:
I see the steps to deploy a cluster in
http://docs.opendaylight.org/en/latest/getting-started-guide/common-features/clustering.html?highlight=clustering
I need to modify *.conf(akka.conf, modules.conf, module-shards.conf) on
each cluster member and then start karaf. Fo
Hi,
I just tried migrating the lispflowmapping integration tests to use our
local Karaf 4 distribution instead of Karaf 3. The integration tests
use org.opendaylight.controller/mdsal-it-parent/1.5.0-SNAPSHOT as the
parent POM.
Unfortunately things don't work out of the box, the container doesn't
13 matches
Mail list logo
