4s-backend-setup(1j) [debian man page]

4S-BACKEND_SETUP(1J)						      4store						      4S-BACKEND_SETUP(1J)

NAME

     4s-backend-setup -- Create a new 4store KB

SYNOPSIS

     4s-backend-setup kbname [--node node-number] [--cluster cluster-size] [--segments segment-count] kb-name

		      --node  Number of this node in the cluster, values range from 0 to cluster-size - 1.  The default is 0.

		      --cluster
			      The number of nodes in the cluster.  The default is 1.

		      --segments
			      The number of segments in the cluster. The default is 2. We recommend one for each CPU core in the cluster as a good
			      starting point. Higher numbers tend to consume more resources, but may result in increased performance.

NOTES

     Once crated with 4s-backend-setup KBs should be started with 4s-backend(1)

SEE ALSO

     4s-query(1), 4s-size(1), 4s-httpd(1), 4s-backend(1), 4s-delete-model(1)

EXAMPLES

     $ 4s-backend-setup --node 0 --cluster 1 --segments 4 demo

     Creates the indexes for a single-machine KB with four segments, named "demo".

4store								   May 31, 2019 							    4store

clinfo(1M)						  System Administration Commands						clinfo(1M)

NAME

       clinfo - display cluster information

SYNOPSIS

       clinfo [-nh]

DESCRIPTION

       The clinfo command displays cluster configuration information about the node from which the command is executed.

       Without	arguments, clinfo returns an exit status of 0 if the node is configured and booted as part of a cluster. Otherwise, clinfo returns
       an exit status of 1.

OPTIONS

       The following options are supported:

       -h    Displays the highest node number allowed to be configured. This is different from the maximum number of nodes supported  in  a  given
	     cluster.  The  current highest configured node number can change immediately after the command returns since new nodes can be dynami-
	     cally added to a running cluster.

	     For example, clinfo -h might return 64, meaning that the highest number you can use to identify a node is 64. See the Sun Cluster 3.0
	     System Administration Guide for a description of utilities you can use to determine the number of nodes in a cluster.

       -n    Prints the number of the node from which clinfo is executed.

EXIT STATUS

       The following exit values are returned:

       0    Successful completion.

       1    An error occurred.

	    This is usually because the node is not configured or booted as part of a cluster.

ATTRIBUTES

       See attributes(5) for descriptions of the following attributes:

       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE	     |	    ATTRIBUTE VALUE	   |
       +-----------------------------+-----------------------------+
       |Availability		     |SUNWcsu			   |
       +-----------------------------+-----------------------------+

SEE ALSO

       attributes(5)

SunOS 5.11							    12 Mar 2002 							clinfo(1M)