Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
From: Subash K <subash.k@ericsson.com>
To: "user@hbase.apache.org" <user@hbase.apache.org>
Subject: Hbase Snapshot Export Data storage
Thread-Topic: Hbase Snapshot Export Data storage
Thread-Index: AdN6FU+WaechmTaaQ+S83sr0t+M6lg==
Date: Thu, 21 Dec 2017 04:36:53 +0000
Message-ID: <AM0PR0702MB3731C8AC10465F8730ACD06EF20D0@AM0PR0702MB3731.eurprd07.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
received-spf: None (protection.outlook.com: ericsson.com does not designate
 permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative;
	boundary="_000_AM0PR0702MB3731C8AC10465F8730ACD06EF20D0AM0PR0702MB3731_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: c3597c17-eead-4305-6cfe-08d5482c75cc
X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Dec 2017 04:36:53.4104
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM0PR0702MB3539
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA02Se0hTYRjG+XbOzo6rxWlqvqlFDBykNi+lmEqYSViS9V9zlTn1oNbcZMc0
	tWgRSU6ETEydiBpmo2aJWV5KykukZoSi3UzIVDbLImdg3jKPn4L//b7neV7eCx9NSCuErnSK
	Np3Va9UaGSUmy5RN0XuSgkNUvgOd24PM5beIMBTZUviFPIFU4tBEVpOSwep9DsSJky1LNiqt
	Nfpid95xA6qPMCIHGph90GldIo1ITEuZTgRTD15R+NGNoOXOm1WHZAoImK0fFPAlUqZMAO1/
	T+OUdSVlL6V4g2Lk8Ng4IeTZidkLE9aaVXZkvKCiq4zCui8sDluREdErrIDhkixeJhkPME2/
	JXiWMHEwZCgW8YyYbTDba1ntSzAu8Hm8UoDHZqDm+TsCszNMjv0TYt4FhtF+EeYdMFCZj/g5
	gekSQXmDjcSGAp4U/kSYj8G12y0EDjUjuDrYuhbyhtr89wI8hRIaJ4rXCnRQ/WlurVsUNPV+
	IHHxIwIKzSUCfjNg3CHv6yaceSGEqt4ofDkW7tVdR/gorjAymIduIk/ThuUw68BWtCQyrR5j
	K/SUjZNY94aqZ3YKsxfUVv8g1rnv5Zhgo16FRPeRM8dy8alJ/v4KVp+SwHE6rULLpjeglU/T
	3rjg24wmrQc7EEMj2WbJwz/BKqlQncFlpXYgoAmZkyRnZr9KKklUZ2Wzet1Z/QUNy3UgN5qU
	uUh6jkhUUiZJnc6eZ9k0Vr/uCmgHVwOiwvMr7S5tAY7pcuWv+slT00GG8cDdcqObZtQCmX5N
	4knH7ws5ki3zgVcSzxx9razpyt252LasPakrj1GGeoR/LDR3+gT8ngs7XHTJVjv/LTc512wa
	GqoTXs5czo4Pu3tj5mlpjGIqIU9ujz1U2+/hzo1oTFnnEkLmC2ItEX2RMpJLVvt5EnpO/R+t
	VFVbMAMAAA==
archived-at: Thu, 21 Dec 2017 04:37:07 -0000

--_000_AM0PR0702MB3731C8AC10465F8730ACD06EF20D0AM0PR0702MB3731_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

We have a use case to transfer data from one cluster to another cluster. As=
 of now we are using CopyTable, but it is having impact on region server an=
d it is taking lot of time to complete data transfer from one to another.

So we are exploring on HBase Export Snapshot feature and we have planned to=
 go ahead with the below steps.


  1.  Take snapshot of a table in Source
  2.  Execute ExportSnapshot job and send the snapshot to the destination
  3.  Restore the snapshot sent from source.
  4.  Now we are able to access the data.

We want to understand how the data is handled in destination after restorin=
g the snapshot. Because we can still see the data under /hbase/archive/data=
 directory in HDFS and only reference data is being maintained in /hbase/da=
ta/

Can someone help us to understand

  1.  When the data under /hbase/archive/data will be removed?
  2.  When new data is inserted into the table, where the data will be stor=
ed either in /hbase/archive/data or /hbase/data?
  3.  I tried to delete the snapshot and run major_compaction for the table=
, the data got moved from /hbase/archive/data to /hbase /data. So, is major=
_compaction required always after restoring snapshot to move the data to it=
s respective data location?
  4.  I'm able to see that data is being stored in archive even if there is=
 no snapshot. Under what other scenario data will be stored in /hbase/archi=
ve/data/ ?

Regards,
Subash Kunjupillai


--_000_AM0PR0702MB3731C8AC10465F8730ACD06EF20D0AM0PR0702MB3731_--