Re: Artemis 2.0 upgrade Shared datastore

One thing is certain. It should work. If not we should fix it. On Wed, May 17, 2017 at 7:33 PM Clebert Suconic wrote: > I think it will work. > > That's an area Justin Bertram and Martyn Taylor worked closer. I will let > them answer. > > > I can do some research

Re: Artemis 2.0 upgrade Shared datastore

I think it will work. That's an area Justin Bertram and Martyn Taylor worked closer. I will let them answer. I can do some research about it tomorrow if they are out tomorrow for any reason. On Wed, May 17, 2017 at 6:53 PM abhijith wrote: > Thanks for the info.

Re: Artemis 2.0 upgrade Shared datastore

Thanks for the info. I am assuming you are referring to `data` option present on server/bin/artemis and not distribution. Please let me know if both are same. Another question on migration, Will 1.4 clients work with 2.0 or they have to migrate. I was hoping they can continue to work with 1.4

Re: Artemis 2.0 upgrade Shared datastore

there's also the convert tool for the config. I recommend you testing (of course) the migration path somewhere outside of production. On Wed, May 17, 2017 at 4:26 PM, abhijith wrote: > Hi, > > We have a shared datastore setup and are currently running v1.4. We are

Re: Artemis 2.0 upgrade Shared datastore

It's not. You have to export and import it again. The address names won't require prefixes. On Wed, May 17, 2017 at 4:39 PM abhijith wrote: > Hi, > > We have a shared datastore setup and are currently running v1.4. We are > planning to upgrade to v2.1 with the

Artemis 2.0 upgrade Shared datastore

Hi, We have a shared datastore setup and are currently running v1.4. We are planning to upgrade to v2.1 with the same configuration. One of the question which came up was if datastore itself compatible with 2 major versions? If we have to rollback v2.1 for some reason will it work seamlessly