Bruce

Admin tool should allow users to initialize replication nodes that are already in config DB

Details

  • Type: Improvement Improvement
  • Status: Open Open
  • Priority: Minor Minor
  • Resolution: Unresolved
  • Affects Version/s: 0.5
  • Fix Version/s: 1.5
  • Component/s: Admin Tool
  • Labels:
    None
  • Number of attachments :
    0

Description

When using the admin tool, if an error occurs for some reason - let's say the database for a node you are loading doesn't exist - the node has already been added to the configuration database, but has not been initialized with the replication schema. There should be an easy way to initialize specific nodes without modifying the configuration database.

Activity

Hide
Lance Ball added a comment -

There is a workaround for this. Submit the XML file for the nodes you need to have initialized, and use "-operation UPDATE" command line option. This will cause the node metadata to be updated in the configuration database, and then initialize the node.

Show
Lance Ball added a comment - There is a workaround for this. Submit the XML file for the nodes you need to have initialized, and use "-operation UPDATE" command line option. This will cause the node metadata to be updated in the configuration database, and then initialize the node.
Hide
Lance Ball added a comment -

Moving this to the next release. There is a reasonable work around for the problem that has no identifiable problems.

Show
Lance Ball added a comment - Moving this to the next release. There is a reasonable work around for the problem that has no identifiable problems.

People

Vote (0)
Watch (0)

Dates

  • Due:
    Created:
    Updated:

Time Tracking

Estimated:
8h
Original Estimate - 8 hours
Remaining:
8h
Remaining Estimate - 8 hours
Logged:
Not Specified
Time Spent - Not Specified