Custom replica placement possible during collection restore

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Custom replica placement possible during collection restore

Kommu, Vinodh K.
Hi,

Would it be possible to restore a collection with replica placement into specific nodes/VMs in the cluster? I guess by default restore feature may not work in such custom way so by any chance can we modify those code details in collection_state.json file in backup directory to place replicas on specific nodes/VMs?

Perhaps it may not be recommended way but would like to know whether this approach will work at all?

Thanks & Regards,
Vinodh

DTCC DISCLAIMER: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error, please notify us immediately and delete the email and any attachments from your system. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. Message content created by DTCC is automatically secured using Transport Layer Security (TLS) encryption and will be encrypted and sent through a secure transmission connection if the recipient's system is configured to support TLS on the incoming email gateway. If there is no TLS configured or the encryption certificate is invalid on the recipient's system, the email communication will be sent through an unencrypted channel. Organizations communicating with DTCC should be using TLS v1.2 or newer to ensure continuation of encrypted communications. DTCC will not be responsible for any disclosure of private information or any related security incident resulting from an organization's inability to receive secure electronic communications through the current version of TLS.
Reply | Threaded
Open this post in threaded view
|

Re: Custom replica placement possible during collection restore

Sean Rasmussen
Hey Vinodh,

I’d have to check the backup/restore process. But I believe that the
state.json file does get exported. If that is the case then the nodesets
should be persisted.

Thanks,
Sean


On October 16, 2020 at 1:22:47 PM, Kommu, Vinodh K. ([hidden email]) wrote:

Hi,

Would it be possible to restore a collection with replica placement into
specific nodes/VMs in the cluster? I guess by default restore feature may
not work in such custom way so by any chance can we modify those code
details in collection_state.json file in backup directory to place replicas
on specific nodes/VMs?

Perhaps it may not be recommended way but would like to know whether this
approach will work at all?

Thanks & Regards,
Vinodh

DTCC DISCLAIMER: This email and any files transmitted with it are
confidential and intended solely for the use of the individual or entity to
whom they are addressed. If you have received this email in error, please
notify us immediately and delete the email and any attachments from your
system. The recipient should check this email and any attachments for the
presence of viruses. The company accepts no liability for any damage caused
by any virus transmitted by this email. Message content created by DTCC is
automatically secured using Transport Layer Security (TLS) encryption and
will be encrypted and sent through a secure transmission connection if the
recipient's system is configured to support TLS on the incoming email
gateway. If there is no TLS configured or the encryption certificate is
invalid on the recipient's system, the email communication will be sent
through an unencrypted channel. Organizations communicating with DTCC
should be using TLS v1.2 or newer to ensure continuation of encrypted
communications. DTCC will not be responsible for any disclosure of private
information or any related security incident resulting from an
organization's inability to receive secure electronic communications
through the current version of TLS.