Olivier Fambon wrote:
Alex [19/10/07 16:59]:
Olivier Fambon wrote:
You can load the first vdb part with option "init", this will tell
the system you are doing an init and bypass the last-man-down check.
Thanks, useful tip!
Well, this is not a tip, this is the way you should do it :)
Hokay!
I've tried just using an init parameter on the command line but no dice:
$ ./controller.sh init
16:37:02,407 FATAL controller.core.Controller Syntax error: unrecognized
option : init
usage: controller(.sh|.bat) [options]
Launchs the Sequoia controller
Options:
-r,--rmi Optional JMX server RMI-Adaptor port number (the default is:
1090 ). Also enables jmx.
-j,--jmx Optional JMX server HTTP-Adaptor port number (the
default is:
8090 ). Also enables jmx.
-f,--file The optional configuration file to init the controller.
-h,--help Displays usage information.
-i,--ip Optional IP address (the default is: 192.168.0.128 )
-p,--port Specify the port the controller is listening on (the
default is:
25322)
-v,--version Displays version information.
I see there is a file option. Should 'init' go in a file that is
identified with the -f option?
Otherwise, you may id of the recovery log for the first controller
you start.
Is this a logfile you are referring to, or the database table called
RECOVERY?
The recoverylog is made of a set of tables, so you would want to get
rid of all these tables in the database that you use to store the
recovery log. Depending on your choice for the recovery log db, this
might mean removing hsqldb files or just dropping/creating the
database in mysql or whatever dbms you use.
Yup, I see....
However, you should be able do get-away with the the "init" load
option, it is here for that purpose. If it does not work, please file
a bug in jira.
Have a nice week-end,
Thanks, and you too!
Alex
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
