Gemfire: the difference with the --parallel when exporting the partitioned region
search cancel

Gemfire: the difference with the --parallel when exporting the partitioned region

book

Article ID: 376610

calendar_today

Updated On:

Products

VMware Tanzu Gemfire

Issue/Introduction

This guide will tell the difference with --parallel option enabled or not when exporting the data from the partitioned region.

 

 

Resolution

1. parallel option enabled

 

When enabling this --parallel option, it will export local data on each node to a directory on that machine.  For example, you have three cache servers and each server will generate a exported gfd file and you will get three gfd files finally.

 

gfsh>list members
Member Count : 4

  Name   | Id
-------- | ------------------------------------------------------------
locator1 | test(locator1:17377:locator)<ec><v0>:41000 [Coordinator]
server1  | test(server1:17598)<v1>:41001
server2  | test(server2:17705)<v2>:41002
server3  | test(server3:17819)<v3>:41003

gfsh>

 

 

 

 

export data --region=/demo1 --member=server1 --parallel=yes --dir=/tmp/gemfire-data

 

-rw-r--r--  1 root root   59 Sep  6 00:12 demo1-10211551141001.gfd
-rw-r--r--  1 root root   59 Sep  6 00:12 demo1-10211551141002.gfd
-rw-r--r--  1 root root   44 Sep  6 00:12 demo1-10211551141003.gfd

 

 

 

2. parallel option disabled

You will get only one file for each region when you do not use the --parallel option when exporting the data

 

 

 

Under both scenarios, you can use the import command to load these data into another region:

import data --member=server3 --region=/demo3 --dir=/tmp/gemfire-data

 

 

 

Please refer to below guide to get more information 

https://docs.vmware.com/en/VMware-GemFire/10.1/gf/tools_modules-gfsh-command-pages-export.html