Perform online compaction of SnappyData disk stores.
For secured cluster
./bin/snappy compact-all-disk-stores -locators==<addresses> -auth-provider=<authprovider> -user=<username> -password=<password> -gemfirexd.auth-ldap-search-base=<search-base-values> -gemfirexd.auth-ldap-search-dn=<search-dn-values> -gemfirexd.auth-ldap-search-pw=<password>
For non-secured cluster
./bin/snappy compact-all-disk-stores== <-locators=<addresses>> [-bind-address=<address>] [-<prop-name>=<prop-value>]*
The table describes options for
|-locators||List of locators used to discover members of the distributed system. Supply all locators as comma-separated host:port values. The port is the
|-bind-address||The address to which this peer binds for receiving peer-to-peer messages. By default
|-prop-name prop-value||Any other SnappyData distributed system property.|
|Authentication properties||Refer Authentication Properites.|
When a CRUD operation is performed on a persistent/overflow table, the data is written to the log files. Any pre-existing operation record for the same row becomes obsolete, and SnappyData marks it as garbage. It compacts an old operation log by copying all non-garbage records into the current log and discarding the old files.
Manual compaction can be done for online and offline disk stores. For the online disk store, the current operation log is not available for compaction, no matter how much garbage it contains.
Offline compaction runs in the same way, but without the incoming CRUD operations. Also, because there is no current open log, the compaction creates a new one to get started.
To run manual online compaction, ALLOWFORCECOMPACTION should be set to true while creating a diskstore You can run manual online compaction at any time while the system is running. Oplogs that are eligible for compaction, based on the COMPACTIONTHRESHOLD, are compacted into the current oplog.
./bin/snappy compact-all-disk-stores -locators=locatorhostname:10334 -auth-provider=LDAP -user=snappy1 -password=snappy1 -J-Dgemfirexd.auth-ldap-server=ldap://localhost:389/ -J-Dgemfirexd.auth-ldap-search-base=cn=sales-group,ou=sales,dc=example,dc=com -J-Dgemfirexd.auth-ldap-search-dn=cn=admin,dc=example,dc=com -J-Dgemfirexd.auth-ldap-search-pw=user123 // The following output is displayed: Connecting to distributed system: locators=localhost 18/11/15 17:54:02.964 IST main<tid=0x1> INFO SNAPPY: TraceAuthentication: Enabling authorization for auth provider LDAP 18/11/15 17:54:03.757 IST main<tid=0x1> INFO SnappyUnifiedMemoryManager: BootTimeMemoryManager org.apache.spark.memory.SnappyUnifiedMemoryManager@11a82d0f configuration: Total Usable Heap = 786.2 MB (824374722) Storage Pool = 393.1 MB (412187361) Execution Pool = 393.1 MB (412187361) Max Storage Pool Size = 628.9 MB (659499777) Compaction complete. The following disk stores compacted some files: