On Tue, Jul 25, 2017 at 5:49 PM, Sam Hague <sha...@redhat.com> wrote:
> > > On Mon, Jul 24, 2017 at 11:28 AM, Muthukumaran K < > muthukumara...@ericsson.com> wrote: > >> Hi Robert, >> >> >> >> This is in context of the changes for BZ-5280. We would like to test the >> changes on master branch. Have some clarifications on the same >> >> >> >> a) Since this change had been major, as I recollect, there was a >> discussion earlier on isolating the changed code-path and old code path. Is >> the new code-path enabled by default on master ? To utilize changed >> code-path, >> >> a) any specific configuration changes in any cfg files (eg. >> Datastore cfg) required or >> >> b) a new type of Databroker to be used to use the changed codepath >> ? In case of new databroker type, if there is any sample usage, can we get >> some pointer for the same ? >> >> >> >> b) Can the changes be tested for specific AskTimeout scenarios - >> encountered earlier, like >> >> a) scaled transactions with and without Transaction Chain (if Txn >> Chain is used, do we still have to use pingpong broker for better results >> ?) of course with appropriate heap-sizing and using G1GC >> >> b) split-brain healing with medium volume of config-data – >> specifically , full split (eg. Downing node interfaces and bringing them >> back up after brief period) and heal of cluster with and without ongoing >> transactions. For completion sake, we can also test partial split and heal >> >> >> >> Any other specific variances of above scenario which could put the >> changes to test ? >> > Robert, do you have any ideas on how we can update our CSIT to test these > changes? Someone mentioned there might just be some config that we can set > and the new code will take effect. Or do we first need to update netvirt > code to make sue of the mdsal changes? > It is not on by by default yet. Set "use-tell-based-protocol=true" in the .cfg file. > >> >> Regards >> >> Muthu >> >> >> >> >> >> _______________________________________________ >> controller-dev mailing list >> controller-dev@lists.opendaylight.org >> https://lists.opendaylight.org/mailman/listinfo/controller-dev >> >> > > _______________________________________________ > controller-dev mailing list > controller-dev@lists.opendaylight.org > https://lists.opendaylight.org/mailman/listinfo/controller-dev > >
_______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev
