Bug 894333
| Summary: | Implement Drop in source migrator for JDG 6.0.x | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Data Grid 6 | Reporter: | Tristan Tarrant <ttarrant> |
| Component: | Server | Assignee: | Tristan Tarrant <ttarrant> |
| Status: | CLOSED WONTFIX | QA Contact: | Martin Gencur <mgencur> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.1.0 | CC: | gsheldon, jdg-bugs, mhusnain, myarboro |
| Target Milestone: | --- | ||
| Target Release: | 6.1.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Known Issue | |
| Doc Text: |
While JBoss Data Grid 6.1 has introduced support for rolling upgrades via Hot Rod, JBoss Data Grid 6.0 is lacking functionality which would enable a rolling upgrade from that version to a newer version. It is therefore not possible to perform a rolling upgrade from JBoss Data Grid 6.0 to JBoss Data Grid 6.1.
</para>
<para>
The JBoss Data Grid 6.0 instance should be configured with a persistent cache store so that all states are persisted to it. After shutting down the JBoss Data Grid 6.0 instance, a JBoss Data Grid 6.1 instance, configured to retrieve the persistent state from the same cache store, can be started in its place. An upgrade from JBoss Data Grid 6.0 to JBoss Data Grid 6.1 is not a seamless operation but requires a complete shutdown of the system in order to be performed.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-02-13 15:21:13 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Tristan Tarrant
2013-01-11 13:15:55 UTC
|