Directory ApacheDS
  1. Directory ApacheDS
  2. DIRSERVER-1789

Changes to an existing replication consumer may not be taken into account

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Critical Critical
    • Resolution: Won't Fix
    • Affects Version/s: 2.0.0-M9
    • Fix Version/s: 2.0.0-M10
    • Component/s: None
    • Labels:
      None

      Description

      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.

        Activity

        Hide
        Emmanuel Lecharny added a comment -

        Closed all the resolved issues

        Show
        Emmanuel Lecharny added a comment - Closed all the resolved issues
        Hide
        Pierre-Arnaud Marcelot added a comment -

        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.

        Show
        Pierre-Arnaud Marcelot added a comment - 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.

          People

          • Assignee:
            Kiran Ayyagari
            Reporter:
            Pierre-Arnaud Marcelot
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development