The Import/Export route won't have any downtime on the "source" system.
You can clone the source table, and use that to run the export. On the
"destination" system, yes, you will only have the data since the last
import.
One thing I didn't think about before is that I'm not sure you can
import to a table that already exists. If you're doing this on a regular
schedule, you would have to do some extra coordination. These snapshots
are full-snapshosts. There is no incremental snapshot support.
As the source table grow, yes, copying the data from one system to the
other (typically, using distcp) will take more and more time.
The above limitations are the base for what the replication feature aims
to solve. Import/Export table, however, are much more simple and
well-tested than replication.
z11373 wrote:
Thanks Josh for the links.
It seems to me if we're going with ImportTable, it'll incur downtime when
importing the data to target table?
Also, the table is growing as the time goes, so the whole export/import
table process may take longer time going forward, is that correct?
Thanks,
Z
--
View this message in context:
http://apache-accumulo.1065345.n5.nabble.com/sync-datacenter-tp15087p15090.html
Sent from the Developers mailing list archive at Nabble.com.
