directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pierre-Arnaud Marcelot (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (DIRSERVER-1789) Changes to an existing replication consumer may not be taken into account
Date Mon, 28 Jan 2013 14:27:12 GMT

     [ https://issues.apache.org/jira/browse/DIRSERVER-1789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Pierre-Arnaud Marcelot resolved DIRSERVER-1789.
-----------------------------------------------

       Resolution: Won't Fix
    Fix Version/s:     (was: 2.0.0-M11)
                   2.0.0-M10
         Assignee: Kiran Ayyagari

What has been done is that we won't edit the corresponding entry on the provider but instead,
we'll create a new one as if the modified consumer is a new consumer.

Eventually, after some delay, the previous consumer entry on the provider will be removed
and the associated event log queue too.
                
> Changes to an existing replication consumer may not be taken into account
> -------------------------------------------------------------------------
>
>                 Key: DIRSERVER-1789
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1789
>             Project: Directory ApacheDS
>          Issue Type: Bug
>    Affects Versions: 2.0.0-M9
>            Reporter: Pierre-Arnaud Marcelot
>            Assignee: Kiran Ayyagari
>            Priority: Critical
>             Fix For: 2.0.0-M10
>
>
> While testing the replication configuration in the ApacheDS v2 Configuration plugin,
I noticed that changes to an existing replication consumer may not be taken into account.
> If I create a replication consumer, save it and restart the server, the replication is
correctly set up and an entry is created under the "ou=consumers,ou=system" node.
> This entry saves a few values from the replication configuration like the search base,
the alias dereferencing mode, etc.
> If update the configuration of the replication consumer and restart the server again.
The values of the entries are not updated and no longer in sync with the updated configuration.
> In that case, I think the replication may fail.
> I would be great to have support for editing the configuration of the replication consumers.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message