You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Martin Alderson (JIRA)" <ji...@apache.org> on 2007/11/15 15:32:43 UTC
[jira] Created: (DIRSERVER-1101) New replicas may never receive
some recent modifications
New replicas may never receive some recent modifications
--------------------------------------------------------
Key: DIRSERVER-1101
URL: https://issues.apache.org/jira/browse/DIRSERVER-1101
Project: Directory ApacheDS
Issue Type: Bug
Components: mitosis
Affects Versions: 1.5.1
Reporter: Martin Alderson
When a new replica is sent all entries from another replica some of the earlier entries may not be up to date. If, for example, we send the first entry to the new replica then the first entry followed by the last entry are modified in turn at the original replica the new replica will never get the modification to the first entry.
This occurs as the new replica will only ever ask for newer logs than it's current update CSN vector which will be based on the most recently modified entries that it was sent.
I think that before the new replica is allowed to receive any newer logs we will need to go back over each entry that was sent and request the modifications to bring each up to the version it should be at. Throughout this time all local modifications should be rejected as in DIRSERVER-1098.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DIRSERVER-1101) New replicas may never receive
some recent modifications
Posted by "Martin Alderson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12542800 ]
Martin Alderson commented on DIRSERVER-1101:
--------------------------------------------
I think a simple solution for this will be to just make the final update CSN vector in the new replica (after it has received all the entries) be that of the original replica when it started sending the entries. This will mean a lot of modifications will be sent that have already been applied but they will be safely ignored by the new replica.
> New replicas may never receive some recent modifications
> --------------------------------------------------------
>
> Key: DIRSERVER-1101
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1101
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: mitosis
> Affects Versions: 1.5.1
> Reporter: Martin Alderson
>
> When a new replica is sent all entries from another replica some of the earlier entries may not be up to date. If, for example, we send the first entry to the new replica then the first entry followed by the last entry are modified in turn at the original replica the new replica will never get the modification to the first entry.
> This occurs as the new replica will only ever ask for newer logs than it's current update CSN vector which will be based on the most recently modified entries that it was sent.
> I think that before the new replica is allowed to receive any newer logs we will need to go back over each entry that was sent and request the modifications to bring each up to the version it should be at. Throughout this time all local modifications should be rejected as in DIRSERVER-1098.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (DIRSERVER-1101) New replicas may never receive some
recent modifications
Posted by "Kiran Ayyagari (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kiran Ayyagari closed DIRSERVER-1101.
-------------------------------------
Assignee: Kiran Ayyagari (was: Martin Alderson)
Resolution: Won't Fix
Mitosis is no longer present in the server, a new replication system is has been developed based on RC 4533
> New replicas may never receive some recent modifications
> --------------------------------------------------------
>
> Key: DIRSERVER-1101
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1101
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: mitosis
> Affects Versions: 1.5.1
> Reporter: Martin Alderson
> Assignee: Kiran Ayyagari
> Fix For: 2.0.0-RC1
>
>
> When a new replica is sent all entries from another replica some of the earlier entries may not be up to date. If, for example, we send the first entry to the new replica then the first entry followed by the last entry are modified in turn at the original replica the new replica will never get the modification to the first entry.
> This occurs as the new replica will only ever ask for newer logs than it's current update CSN vector which will be based on the most recently modified entries that it was sent.
> I think that before the new replica is allowed to receive any newer logs we will need to go back over each entry that was sent and request the modifications to bring each up to the version it should be at. Throughout this time all local modifications should be rejected as in DIRSERVER-1098.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DIRSERVER-1101) New replicas may never receive
some recent modifications
Posted by "Martin Alderson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Alderson updated DIRSERVER-1101:
---------------------------------------
Fix Version/s: (was: 1.5.2)
1.5.3
Postponing.
> New replicas may never receive some recent modifications
> --------------------------------------------------------
>
> Key: DIRSERVER-1101
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1101
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: mitosis
> Affects Versions: 1.5.1
> Reporter: Martin Alderson
> Assignee: Martin Alderson
> Fix For: 1.5.3
>
>
> When a new replica is sent all entries from another replica some of the earlier entries may not be up to date. If, for example, we send the first entry to the new replica then the first entry followed by the last entry are modified in turn at the original replica the new replica will never get the modification to the first entry.
> This occurs as the new replica will only ever ask for newer logs than it's current update CSN vector which will be based on the most recently modified entries that it was sent.
> I think that before the new replica is allowed to receive any newer logs we will need to go back over each entry that was sent and request the modifications to bring each up to the version it should be at. Throughout this time all local modifications should be rejected as in DIRSERVER-1098.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (DIRSERVER-1101) New replicas may never receive
some recent modifications
Posted by "Martin Alderson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Alderson reassigned DIRSERVER-1101:
------------------------------------------
Assignee: Martin Alderson
I now have a fix for this in my private copy of mitosis which just needs porting / committing.
> New replicas may never receive some recent modifications
> --------------------------------------------------------
>
> Key: DIRSERVER-1101
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1101
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: mitosis
> Affects Versions: 1.5.1
> Reporter: Martin Alderson
> Assignee: Martin Alderson
>
> When a new replica is sent all entries from another replica some of the earlier entries may not be up to date. If, for example, we send the first entry to the new replica then the first entry followed by the last entry are modified in turn at the original replica the new replica will never get the modification to the first entry.
> This occurs as the new replica will only ever ask for newer logs than it's current update CSN vector which will be based on the most recently modified entries that it was sent.
> I think that before the new replica is allowed to receive any newer logs we will need to go back over each entry that was sent and request the modifications to bring each up to the version it should be at. Throughout this time all local modifications should be rejected as in DIRSERVER-1098.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DIRSERVER-1101) New replicas may never receive
some recent modifications
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Karasulu updated DIRSERVER-1101:
-------------------------------------
Cool thanks for the heads up. I guess 1.5.4 or there after is best for a settled API. Let me push this off to 1.5.5 which is on our roadmap here:
http://cwiki.apache.org/confluence/display/DIRxPMGT/2.0+Roadmap
I realized the flux was making it hard to keep up so we kind of pushed things off a tiny bit.
> New replicas may never receive some recent modifications
> --------------------------------------------------------
>
> Key: DIRSERVER-1101
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1101
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: mitosis
> Affects Versions: 1.5.1
> Reporter: Martin Alderson
> Assignee: Martin Alderson
> Fix For: 1.5.3
>
>
> When a new replica is sent all entries from another replica some of the earlier entries may not be up to date. If, for example, we send the first entry to the new replica then the first entry followed by the last entry are modified in turn at the original replica the new replica will never get the modification to the first entry.
> This occurs as the new replica will only ever ask for newer logs than it's current update CSN vector which will be based on the most recently modified entries that it was sent.
> I think that before the new replica is allowed to receive any newer logs we will need to go back over each entry that was sent and request the modifications to bring each up to the version it should be at. Throughout this time all local modifications should be rejected as in DIRSERVER-1098.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DIRSERVER-1101) New replicas may never receive
some recent modifications
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny updated DIRSERVER-1101:
-----------------------------------------
Fix Version/s: (was: 1.5.7)
2.0.0-RC1
Moved to 2.0.0-RC1, we won't release a 1.5.7
> New replicas may never receive some recent modifications
> --------------------------------------------------------
>
> Key: DIRSERVER-1101
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1101
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: mitosis
> Affects Versions: 1.5.1
> Reporter: Martin Alderson
> Assignee: Martin Alderson
> Fix For: 2.0.0-RC1
>
>
> When a new replica is sent all entries from another replica some of the earlier entries may not be up to date. If, for example, we send the first entry to the new replica then the first entry followed by the last entry are modified in turn at the original replica the new replica will never get the modification to the first entry.
> This occurs as the new replica will only ever ask for newer logs than it's current update CSN vector which will be based on the most recently modified entries that it was sent.
> I think that before the new replica is allowed to receive any newer logs we will need to go back over each entry that was sent and request the modifications to bring each up to the version it should be at. Throughout this time all local modifications should be rejected as in DIRSERVER-1098.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DIRSERVER-1101) New replicas may never receive
some recent modifications
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny updated DIRSERVER-1101:
-----------------------------------------
Fix Version/s: 1.5.2
Martin, if you have a fix for this issue, bigbang will remain available for 2 more days, then we will postpone to 1.5.3.
> New replicas may never receive some recent modifications
> --------------------------------------------------------
>
> Key: DIRSERVER-1101
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1101
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: mitosis
> Affects Versions: 1.5.1
> Reporter: Martin Alderson
> Assignee: Martin Alderson
> Fix For: 1.5.2
>
>
> When a new replica is sent all entries from another replica some of the earlier entries may not be up to date. If, for example, we send the first entry to the new replica then the first entry followed by the last entry are modified in turn at the original replica the new replica will never get the modification to the first entry.
> This occurs as the new replica will only ever ask for newer logs than it's current update CSN vector which will be based on the most recently modified entries that it was sent.
> I think that before the new replica is allowed to receive any newer logs we will need to go back over each entry that was sent and request the modifications to bring each up to the version it should be at. Throughout this time all local modifications should be rejected as in DIRSERVER-1098.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DIRSERVER-1101) New replicas may never receive
some recent modifications
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Karasulu updated DIRSERVER-1101:
-------------------------------------
Fix Version/s: (was: 1.5.3)
1.5.5
Ooops forgot to adjust the fix version.
> New replicas may never receive some recent modifications
> --------------------------------------------------------
>
> Key: DIRSERVER-1101
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1101
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: mitosis
> Affects Versions: 1.5.1
> Reporter: Martin Alderson
> Assignee: Martin Alderson
> Fix For: 1.5.5
>
>
> When a new replica is sent all entries from another replica some of the earlier entries may not be up to date. If, for example, we send the first entry to the new replica then the first entry followed by the last entry are modified in turn at the original replica the new replica will never get the modification to the first entry.
> This occurs as the new replica will only ever ask for newer logs than it's current update CSN vector which will be based on the most recently modified entries that it was sent.
> I think that before the new replica is allowed to receive any newer logs we will need to go back over each entry that was sent and request the modifications to bring each up to the version it should be at. Throughout this time all local modifications should be rejected as in DIRSERVER-1098.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DIRSERVER-1101) New replicas may never receive
some recent modifications
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12606197#action_12606197 ]
Alex Karasulu commented on DIRSERVER-1101:
------------------------------------------
Can I get a status on this? Did you commit your changes?
> New replicas may never receive some recent modifications
> --------------------------------------------------------
>
> Key: DIRSERVER-1101
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1101
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: mitosis
> Affects Versions: 1.5.1
> Reporter: Martin Alderson
> Assignee: Martin Alderson
> Fix For: 1.5.3
>
>
> When a new replica is sent all entries from another replica some of the earlier entries may not be up to date. If, for example, we send the first entry to the new replica then the first entry followed by the last entry are modified in turn at the original replica the new replica will never get the modification to the first entry.
> This occurs as the new replica will only ever ask for newer logs than it's current update CSN vector which will be based on the most recently modified entries that it was sent.
> I think that before the new replica is allowed to receive any newer logs we will need to go back over each entry that was sent and request the modifications to bring each up to the version it should be at. Throughout this time all local modifications should be rejected as in DIRSERVER-1098.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DIRSERVER-1101) New replicas may never receive
some recent modifications
Posted by "Martin Alderson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12606526#action_12606526 ]
Martin Alderson commented on DIRSERVER-1101:
--------------------------------------------
Negative. I put it off while there was a large amount of flux around the API / bigbang branch and the configuration. It seems to be settling down now so will look into putting some time aside for mitosis soon.
> New replicas may never receive some recent modifications
> --------------------------------------------------------
>
> Key: DIRSERVER-1101
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1101
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: mitosis
> Affects Versions: 1.5.1
> Reporter: Martin Alderson
> Assignee: Martin Alderson
> Fix For: 1.5.3
>
>
> When a new replica is sent all entries from another replica some of the earlier entries may not be up to date. If, for example, we send the first entry to the new replica then the first entry followed by the last entry are modified in turn at the original replica the new replica will never get the modification to the first entry.
> This occurs as the new replica will only ever ask for newer logs than it's current update CSN vector which will be based on the most recently modified entries that it was sent.
> I think that before the new replica is allowed to receive any newer logs we will need to go back over each entry that was sent and request the modifications to bring each up to the version it should be at. Throughout this time all local modifications should be rejected as in DIRSERVER-1098.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DIRSERVER-1101) New replicas may never receive
some recent modifications
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny updated DIRSERVER-1101:
-----------------------------------------
Fix Version/s: (was: 1.5.5)
1.5.7
Moved to 1.5.7, where Mitosis will be reviewed
> New replicas may never receive some recent modifications
> --------------------------------------------------------
>
> Key: DIRSERVER-1101
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1101
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: mitosis
> Affects Versions: 1.5.1
> Reporter: Martin Alderson
> Assignee: Martin Alderson
> Fix For: 1.5.7
>
>
> When a new replica is sent all entries from another replica some of the earlier entries may not be up to date. If, for example, we send the first entry to the new replica then the first entry followed by the last entry are modified in turn at the original replica the new replica will never get the modification to the first entry.
> This occurs as the new replica will only ever ask for newer logs than it's current update CSN vector which will be based on the most recently modified entries that it was sent.
> I think that before the new replica is allowed to receive any newer logs we will need to go back over each entry that was sent and request the modifications to bring each up to the version it should be at. Throughout this time all local modifications should be rejected as in DIRSERVER-1098.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.