[JBoss JIRA] Created: (JBMESSAGING-1742) Allow the clustered status of a destination to be updated without the need for manually intervention.
5:43 a.m.
Allow the clustered status of a destination to be updated without the need for manually
intervention.
-----------------------------------------------------------------------------------------------------
Key: JBMESSAGING-1742
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1742
Project: JBoss Messaging
Issue Type: Feature Request
Affects Versions: 1.4.0.SP3.CP09
Reporter: Colin Mondesir
Assignee: Howard Gao
Priority: Minor
At the moment when a destination is deployed as non clustered, then redeployed as
clustered, the clustered attribute in the JBM_POSTOFFICE table is not updated.
In order to change the clustered status of a destination you need to delete the original
destination from storage first.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:06 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1742) Allow the clustered status of a destination to be updated without the need for manually intervention.
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1742?page=com.atlassian.ji...
]
Howard Gao updated JBMESSAGING-1742:
------------------------------------
Fix Version/s: 1.4.0.SP3.CP10
1.4.7.GA
Affects Version/s: 1.4.6.GA
1.4.5.GA
Allow the clustered status of a destination to be updated without the
need for manually intervention.
-----------------------------------------------------------------------------------------------------
Key: JBMESSAGING-1742
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1742
Project: JBoss Messaging
Issue Type: Feature Request
Affects Versions: 1.4.0.SP3.CP09, 1.4.5.GA, 1.4.6.GA
Reporter: Colin Mondesir
Assignee: Howard Gao
Priority: Minor
Fix For: 1.4.0.SP3.CP10, 1.4.7.GA
At the moment when a destination is deployed as non clustered, then redeployed as
clustered, the clustered attribute in the JBM_POSTOFFICE table is not updated.
In order to change the clustered status of a destination you need to delete the original
destination from storage first.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:09 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1742) Allow the clustered status of a destination to be updated without the need for manually intervention.
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1742?page=com.atlassian.ji...
]
Howard Gao commented on JBMESSAGING-1742:
-----------------------------------------
Here is where I'm working towards:
In QueueService.start() (TopicService), we check the newly deployed destination with the
existing one. There could be two cases:
Case 1. Existing destination clustered but new destination not.
Case 2. Existing destination not clustered but new destination clustered.
In either case, we log a warning and then do the destination conversion. The work should
be given to PostOffice.
postOffice.convertDestination(destination, isClustered); //will do the clean up work if
necessary.
Allow the clustered status of a destination to be updated without the
need for manually intervention.
-----------------------------------------------------------------------------------------------------
Key: JBMESSAGING-1742
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1742
Project: JBoss Messaging
Issue Type: Feature Request
Affects Versions: 1.4.0.SP3.CP09, 1.4.5.GA, 1.4.6.GA
Reporter: Colin Mondesir
Assignee: Howard Gao
Priority: Minor
Fix For: 1.4.0.SP3.CP10, 1.4.7.GA
At the moment when a destination is deployed as non clustered, then redeployed as
clustered, the clustered attribute in the JBM_POSTOFFICE table is not updated.
In order to change the clustered status of a destination you need to delete the original
destination from storage first.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:27 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1742) Allow the clustered status of a destination to be updated without the need for manually intervention.
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1742?page=com.atlassian.ji...
]
Howard Gao commented on JBMESSAGING-1742:
-----------------------------------------
One possible concern is the existing messages in the DB.
Here we may provide an configure parameter dropOldMessageOnRedeploy, if set true, we
simply clean up all the messages. if set false, we preserve the messages and load them
after the destination has been converted.
Allow the clustered status of a destination to be updated without the
need for manually intervention.
-----------------------------------------------------------------------------------------------------
Key: JBMESSAGING-1742
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1742
Project: JBoss Messaging
Issue Type: Feature Request
Affects Versions: 1.4.0.SP3.CP09, 1.4.5.GA, 1.4.6.GA
Reporter: Colin Mondesir
Assignee: Howard Gao
Priority: Minor
Fix For: 1.4.0.SP3.CP10, 1.4.7.GA
At the moment when a destination is deployed as non clustered, then redeployed as
clustered, the clustered attribute in the JBM_POSTOFFICE table is not updated.
In order to change the clustered status of a destination you need to delete the original
destination from storage first.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:22 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1742) Allow the clustered status of a destination to be updated without the need for manually intervention.
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1742?page=com.atlassian.ji...
]
Howard Gao commented on JBMESSAGING-1742:
-----------------------------------------
I'm assuming the following usage:
1. non-cluster destination --> clustered destination:
User changes the clustered attribute to 'true' and then may add as many as
possible new destinations to other nodes. Existing messages can be safely removed from DB
or remain without any change.
2. clustered destination ---> non clustered destination:
User keeps only one of the destination's config file and manually delete all other
configuration files of the clustered destination. Then he modified the destination's
clustered attribute to be 'false'. Then redeploy it.
Note:
In both cases, it is required that the user shut down all nodes before making any of the
changes.
Allow the clustered status of a destination to be updated without the
need for manually intervention.
-----------------------------------------------------------------------------------------------------
Key: JBMESSAGING-1742
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1742
Project: JBoss Messaging
Issue Type: Feature Request
Affects Versions: 1.4.0.SP3.CP09, 1.4.5.GA, 1.4.6.GA
Reporter: Colin Mondesir
Assignee: Howard Gao
Priority: Minor
Fix For: 1.4.0.SP3.CP10, 1.4.7.GA
At the moment when a destination is deployed as non clustered, then redeployed as
clustered, the clustered attribute in the JBM_POSTOFFICE table is not updated.
In order to change the clustered status of a destination you need to delete the original
destination from storage first.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:59 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1742) Allow the clustered status of a destination to be updated without the need for manually intervention.
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1742?page=com.atlassian.ji...
]
Howard Gao updated JBMESSAGING-1742:
------------------------------------
Fix Version/s: 1.4.6.GA.SP1
Allow the clustered status of a destination to be updated without the
need for manually intervention.
-----------------------------------------------------------------------------------------------------
Key: JBMESSAGING-1742
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1742
Project: JBoss Messaging
Issue Type: Feature Request
Affects Versions: 1.4.0.SP3.CP09, 1.4.5.GA, 1.4.6.GA
Reporter: Colin Mondesir
Assignee: Howard Gao
Priority: Minor
Fix For: 1.4.0.SP3.CP10, 1.4.6.GA.SP1, 1.4.7.GA
At the moment when a destination is deployed as non clustered, then redeployed as
clustered, the clustered attribute in the JBM_POSTOFFICE table is not updated.
In order to change the clustered status of a destination you need to delete the original
destination from storage first.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:01 p.m.
New subject: [JBoss JIRA] Closed: (JBMESSAGING-1742) Allow the clustered status of a destination to be updated without the need for manually intervention.
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1742?page=com.atlassian.ji...
]
Howard Gao closed JBMESSAGING-1742.
-----------------------------------
Resolution: Done
Documentation added:
6.6.2.1.18.
6.6.3.1.20.
Allow the clustered status of a destination to be updated without the
need for manually intervention.
-----------------------------------------------------------------------------------------------------
Key: JBMESSAGING-1742
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1742
Project: JBoss Messaging
Issue Type: Feature Request
Affects Versions: 1.4.0.SP3.CP09, 1.4.5.GA, 1.4.6.GA
Reporter: Colin Mondesir
Assignee: Howard Gao
Priority: Minor
Fix For: 1.4.0.SP3.CP10, 1.4.6.GA.SP1, 1.4.7.GA
At the moment when a destination is deployed as non clustered, then redeployed as
clustered, the clustered attribute in the JBM_POSTOFFICE table is not updated.
In order to change the clustered status of a destination you need to delete the original
destination from storage first.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6115
days inactive
6135
days old
6 comments
2 participants
participants (2)
-
Colin Mondesir (JIRA) -
Howard Gao (JIRA)