No need for file difference map when fresh/empty secondary

Appdynamics / HA-toolkit

AppDynamics Controller High Availability Toolkit

https://docs.appdynamics.com/display/PRO42/Using+the+High+Availability+(HA)+Toolkit

Apache License 2.0

13 stars 11 forks source link

No need for file difference map when fresh/empty secondary #98

Closed rnav1234 closed 5 years ago

rnav1234 commented 5 years ago

When a fresh/new/empty secondary is being added then there is no need to calculate the list of differences that need to be deleted from secondary. This step takes ~17mins for 2TB db/data

cmayer68 commented 5 years ago

this is actually a general case. the secondary files should be enumerated and sent back to the primary. only these files need be checksum'ed, and this process should be done in parallel. thus, the total pruning will speed up by at least half, and when doing an initial replicate, be immediate.

rnav1234 commented 5 years ago

Resolved in release v3.50