Re: What can NOT be done during repairs (2.2.x and 3.0.x)
Thanks Erick! On Thu, Nov 9, 2017 at 2:58 AM, Erick Ramirez wrote: > You can continue to perform operations while running a repair but just be > aware that you will get repair failures, e.g. if you drop a table while > that table is getting repaired. In which case, the failure is benign. > > Creating new keyspaces or tables will not pose any problems for the repair > sessions in-flight. Cheers! > > On Tue, Nov 7, 2017 at 3:19 AM, Herbert Fischer < > herbert.fisc...@crossengage.io> wrote: > >> Hello, >> >> I know from DS docs that we must not change the cluster topology while >> there are repairs going on, and vice-versa. >> >> Is there anything else that cannot be done while there are repairs >> happening? Are schema-changes fine? Is creating new keyspaces or tables >> fine? >> >> best, >> >> Herbert >> > > -- Herbert Fischer | Senior IT Architect CrossEngage GmbH | Bertha-Benz Straße 5 | 10557 Berlin E-Mail: herbert.fisc...@crossengage.io Web: www.crossengage.io Amtsgericht Berlin-Charlottenburg | HRB 169537 B Geschäftsführer: Dr. Markus Wübben, Manuel Hinz | USt-IdNr.: DE301504202
Re: What can NOT be done during repairs (2.2.x and 3.0.x)
You can continue to perform operations while running a repair but just be aware that you will get repair failures, e.g. if you drop a table while that table is getting repaired. In which case, the failure is benign. Creating new keyspaces or tables will not pose any problems for the repair sessions in-flight. Cheers! On Tue, Nov 7, 2017 at 3:19 AM, Herbert Fischer < herbert.fisc...@crossengage.io> wrote: > Hello, > > I know from DS docs that we must not change the cluster topology while > there are repairs going on, and vice-versa. > > Is there anything else that cannot be done while there are repairs > happening? Are schema-changes fine? Is creating new keyspaces or tables > fine? > > best, > > Herbert >
What can NOT be done during repairs (2.2.x and 3.0.x)
Hello, I know from DS docs that we must not change the cluster topology while there are repairs going on, and vice-versa. Is there anything else that cannot be done while there are repairs happening? Are schema-changes fine? Is creating new keyspaces or tables fine? best, Herbert
