- 1. Introduction
- 2. Getting Started
- 3. Technical Architecture and Guide
- 4. Data Modeling
-
5. Sample Applications
-
5.1 Basics
- 5.1.1 Introduction
- 5.1.2 GridDB Basics
- 5.1.3 Preparation: Environment (server)
- 5.1.4 Preparation: Environment (client)
- 5.1.5 Preparation: Connecting GridDB
- 5.1.6 Schema definition
- 5.1.7 Container Create / Delete
- 5.1.8 Register Collection
- 5.1.9 Data Retrieval
- 5.1.10 Data Deletion
- 5.1.11 Collection Modification
- 5.1.12 Data Registration
- 5.1.13 Data Retrieval
- 5.1.14 Time-Series Data Deletion
- 5.1.15 Change of Time-Series Container
- 5.1.16 TQL
- 5.1.17 Trigger (REST)
- 5.1.18 Trigger (JMS)
- 5.1.19 Multi-Put
- 5.1.20 Multi-Query
- 5.1.21 Multi-Get
- 5.1.22 Meta-information
-
5.1 Basics
- 6. Administration
- 7. Drivers & Integrators
- Misc.
6.4 Upgrading the Editions
Follow the procedure below to update the software.
- Stop the cluster
- Stop the node
- Make a backup copy of the definition file, database file and event log file
- Update the software
- Start the node
- Configure the cluster
An example of the command execution in a machine in which the nodes have been started is shown below.
[Command execution example]
$ gs_stopcluster -u admin/admin $ gs_stopnode -u admin/admin $ cp -rp /var/lib/gridstore/data /xxx/shelter # copy just in case $ cp -rp /var/lib/gridstore/log /xxx/shelter # copy just in case $ cp -rp /var/lib/gridstore/conf /xxx/shelter # copy just in case $ su # rpm -Uvh griddb-server-Y.Y.Y-linux.x86_64.rpm # rpm -Uvh griddb-client-Y.Y.Y-linux.x86_64.rpm # rpm -Uvh griddb-docs-Y.Y.Y-linux.x86_64.rpm # exit $ gs_startnode $ gs_joincluster -c configured cluster name -u admin/admin
*Y.Y.Y: Version of GridDB to update