Install GridDB On Windows via WSL

Installing and using GridDB on Windows machines is made very easy with the use of Docker. With Docker, we can install GridDB and keep it maintained inside of its own siloed container, complete with its own network environment — if needed. And though this method works brilliantly, sometimes it behooves a developer to run the server in a more accessible way. In this article, we will go over how to install GridDB on Windows machines without the use of Docker or Virtualbox — though the approach is not too different.

Instead of using those technologies, we will instead be utilizing the excellent Windows Subsystem for Linux. Normally shortned to wsl, this subsystem allows developers to “run a GNU/Linux environment — including most command-line tools, utilities, and applications — directly on Windows, unmodified, without the overhead of a traditional virtual machine or dualboot setup.” Basically, this tool provides for a user to run native Windows, but also have access to a Linux command line interface by simply opening up a terminal application your Windows machine — that is the power and flexibility of the wsl.

So in this article, we will go over a basic installation of wsl, and then how to properly install GridDB so that you can reap all of the benefits of running GridDB on your Windows machine.

Installing WSL

To begin, you will need an environment with either Windows 10 or 11. Next, simply open up a Windows powershell or command prompt with raised admin priveleges (right click –> run as admin) and enter the following command:

wsl --install

And that is basically the entirety of it; a much more detailed account of getting started with WSL can be found here.

An important note: from my limited testing, it appears as though enabling systemd (see below) can only be done when installing Ubuntu from directly inside the Microsoft Store as seen here: So if you download Ubuntu from official store, it will appear in your WSL and will work like normal.

Once you install WSL, you will have Ubuntu available to you and can begin the process of installing GridDB. Though, of course, if you prefer CentOS or some other Linux distro, you can run actually run multiple instances of Linux subsystems on your machine — you simply choose which distro you’d like to run and use.

Installing GridDB

You can read about installing GridDB on Ubuntu in the docs:, but here are the basic instructions. What we will do is add the GridDB apt repository into our apt-get sources list so that it knows where to download GridDB. Once it’s added, we can simply run an apt install and it will fetch and install everything you need to get started.

$ sudo sh -c 'echo "deb griddb/5.1 multiverse" >>  /etc/apt/sources.list.d/griddb.list'
$ wget -qO - | sudo apt-key add -

Once this is added, we can simply

$ sudo apt update
$ sudo apt install griddb-meta

The griddb-meta package includes: GridDB server, c_client, jdbc, and GridDB CLI.

Running GridDB On WSL

And now this where we need to deviate a little bit from a normal Ubuntu installation process.

GridDB On WSL with Systemd

By default, the easiest method to run GridDB is through systemd, but unfortunately it is not available on WSL — until recently! And if you are wondering what systemd is, it’s a suite of software which provides a “a “system and service manager” – an init system used to bootstrap user space and manage user processes.” What this means in the context of GridDB is that we can enable GridDB to be run A. on bootup (of WSL), and B. managed by the system.

So, to enable systemd on your WSL instance, use your favorite text editor and open up the following file (or create if it doesn’t exist yet)”

$ sudo vim /etc/wsl.conf

And once it’s open, add the following content:


Now simply restart your WSL with the following command: wsl –shutdown in an elevated powershell or command prompt and reopen your WSL instance.

Now we can start GridDB:

$ sudo systemctl start gridstore

To verify that it’s running you can run sudo systemctl status gridstore. With GridDB running on your WSL, you can now access it via the GridDB CLI or through the NoSQL interface using the following credentials:

user: admin
password: admin
cluster: myCluster
database: public

Using GridDB on WSL Without Systemd

The above method is the easier and preferred method for running GridDB, but if you would prefer to run GridDB in a more ad-hoc sort of way, you can manually start and stop it instead.

To do so, we will login to the GridDB user gsadm which was created for us at the time of the GridDB Installation. From there, we can manually start up GridDB and join the cluster and use GridDB normally.

$ sudo su gsadm
$ gs_startnode -u admin/admin

And note, if you get the following error:

A00105: GS_HOME, GS_LOG environment variable not set.

The error is self-explanatory, but to solve it, you can simply source the gsadm’s .bash_profile file

$  source ~/.bash_profile

And then try again:

$ gs_startnode -u admin/admin

And to join the cluster

$ gs_joincluster -c myCluster -u admin/admin

And then to make sure everything is gravy:

$ gs_stat -u admin/admin
    "checkpoint": {
        "backupOperation": 0,
        "duplicateLog": 0,
        "endTime": 1681163543250,
        "mode": "NORMAL_CHECKPOINT",
        "normalCheckpointOperation": 747,
        "pendingPartition": 0,
        "periodicCheckpoint": "ACTIVE",
        "requestedCheckpointOperation": 0,
        "startTime": 1681163543246
    "cluster": {
        "activeCount": 1,
        "applyRuleLimitTime": "2023-04-07T22:09:04.281-08:00",
        "autoGoal": "ACTIVE",
        "clusterName": "myCluster",
        "clusterRevisionId": "db3ff2a8-319e-42d3-8cb2-5ecf1657e0ad",
        "clusterRevisionNo": 8975,
        "clusterStatus": "MASTER",
        "currentRule": "Initial",
        "designatedCount": 1,
        "loadBalancer": "ACTIVE",
        "master": {
            "address": "",
            "port": 10040
        "nodeList": [
                "address": "",
                "port": 10040
        "nodeStatus": "ACTIVE",
        "notificationMode": "FIXED_LIST",
        "partitionStatus": "NORMAL",
        "startupTime": "2023-04-07T09:40:58.181-08:00",
        "syncCount": 2
    "currentTime": "2023-04-10T13:53:17-08:00",
    "performance": {
        "backgroundMinRate": 0.1,
        "backupCount": 0,
        "checkpointFileFlushCount": 128,
        "checkpointFileFlushTime": 37,
        "checkpointWrite": 0,
        "checkpointWriteCompressTime": 0,
        "checkpointWriteSize": 0,
        "checkpointWriteTime": 0,
        "currentTime": 1681163597511,
        "dataFileAllocateSize": 0,
        "dataFileSize": 0,
        "dataFileUsageRate": 1,
        "expirationDetail": {
            "batchScanNum": 2000,
            "batchScanTotalNum": 0,
            "batchScanTotalTime": 0,
            "erasableExpiredTime": "",
            "estimatedBatchFree": 0,
            "estimatedErasableExpiredTime": "",
            "lastBatchFree": 0,
            "latestExpirationCheckTime": "Under measurement"
        "logFileFlushCount": 256,
        "logFileFlushTime": 385,
        "numBackground": 0,
        "numConnection": 1,
        "numNoExpireTxn": 0,
        "numSession": 0,
        "numTxn": 0,
        "ownerCount": 128,
        "peakProcessMemory": 136179712,
        "poolBufferMemory": 0,
        "processMemory": 136179712,
        "sqlNumConnection": 1,
        "sqlStoreSwapRead": 0,
        "sqlStoreSwapReadSize": 0,
        "sqlStoreSwapReadTime": 0,
        "sqlStoreSwapWrite": 0,
        "sqlStoreSwapWriteSize": 0,
        "sqlStoreSwapWriteTime": 0,
        "storeCompressionMode": "NO_BLOCK_COMPRESSION",
        "storeDetail": {
            "batchFreeMapData": {
                "storeMemory": 0,
                "storeUse": 0,
                "swapRead": 0,
                "swapWrite": 0
            "batchFreeRowData": {
                "storeMemory": 0,
                "storeUse": 0,
                "swapRead": 0,
                "swapWrite": 0
            "mapData": {
                "storeMemory": 0,
                "storeUse": 0,
                "swapRead": 0,
                "swapWrite": 0
            "metaData": {
                "storeMemory": 0,
                "storeUse": 0,
                "swapRead": 0,
                "swapWrite": 0
            "rowData": {
                "storeMemory": 0,
                "storeUse": 0,
                "swapRead": 0,
                "swapWrite": 0
        "storeMemory": 0,
        "storeMemoryLimit": 1073741824,
        "storeTotalUse": 0,
        "swapRead": 0,
        "swapReadSize": 0,
        "swapReadTime": 0,
        "swapReadUncompressTime": 0,
        "swapWrite": 0,
        "swapWriteCompressTime": 0,
        "swapWriteSize": 0,
        "swapWriteTime": 0,
        "totalBackupLsn": 0,
        "totalExternalConnectionCount": 0,
        "totalInternalConnectionCount": 0,
        "totalLockConflictCount": 0,
        "totalOtherLsn": 0,
        "totalOwnerLsn": 0,
        "totalReadOperation": 0,
        "totalRowRead": 0,
        "totalRowWrite": 0,
        "totalWriteOperation": 0,
        "txnDetail": {
            "totalBackgroundOperation": 0
    "recovery": {
        "progressRate": 1
    "version": "5.1.0-39692 CE"

Next Steps

Now that GridDB is installed, the next steps are to install the language connector of your choice and start programming. Much more information can be found here:


And with that, now you can utilize GridDB in a variety of different ways using Windows.

If you have any questions about the blog, please create a Stack Overflow post here .
Make sure that you use the “griddb” tag so our engineers can quickly reply to your questions.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.