-
1. Re: 2.3 vs 2.2 network compatibility
clebert.suconic Dec 11, 2012 6:53 PM (in response to hsn10)clustering between 2.3 and 2.2 won't be supported.
Clients from 2.2 will be able to talk to 2.3... however there's an issue on Beta2 that will be fixed by next release (Beta3 or CR.. TBD yet)
-
2. Re: 2.3 vs 2.2 network compatibility
zepag Apr 13, 2013 4:08 AM (in response to clebert.suconic)What about this?
Is compatibility ensured between 2.2 clients and 2.3 brokers?
I also suppose 2.3 clients will be able to talk to 2.3 brokers.
If I remember well this was to be ensured from version 2.2 and superior versions.
(I'll check the test suites, though I'd like to be sure of the "policy" .
-
3. Re: 2.3 vs 2.2 network compatibility
clebert.suconic Apr 13, 2013 10:25 AM (in response to zepag)I suspect you had a typo on this statement:
" also suppose 2.3 clients will be able to talk to 2.3 brokers."
I assume you meant
" also suppose 2.3 clients will be able to talk to 2.2 brokers."
The policy so far was clientversion <= serverversion. clientversion > serverVersion is not tested and will certainly lead to error.
-
4. Re: 2.3 vs 2.2 network compatibility
zepag Apr 13, 2013 11:47 AM (in response to clebert.suconic)Definitely a typo.
Important thing to know then.
Migration from 2.2 to 2.3 will therefore require to migrate all clients at the same time or after all brokers have migrated to 2.3, but not before.
Thx a lot!
-
5. Re: 2.3 vs 2.2 network compatibility
clebert.suconic Apr 13, 2013 12:31 PM (in response to zepag)a 2.2 client can talk to a 2.3 server (send and receive messages).
You could partition your clusters, right?
-
6. Re: 2.3 vs 2.2 network compatibility
zepag Apr 13, 2013 4:58 PM (in response to clebert.suconic)Well in this case it is more several small independant standalone HornetQ nodes, without cluster in place, so no need to partition them.
Am I missing something or do you mean something else by "partition your clusters"
-
7. Re: 2.3 vs 2.2 network compatibility
clebert.suconic Apr 13, 2013 6:49 PM (in response to zepag)I thought you had a cluster of nodes sharing the load on messaging. I mean you could create a parallel cluster and migrate little by little.
If they are independent you can just migrate the server now.. clients should work. (If they are not working it would be a bug. We test compatibility but who knows if we missed something? I hope not thought).