Hi Manjeet, The HBase indexer hookup on the replication layer to carry the mutations over to SOLR. The impact is the same as for replication (Like, if you stop SOLR forever, the WALs will stay on HBase side, etc.)
You can look at those links: https://www.cloudera.com/documentation/enterprise/latest/topics/cdh_bdr_hbase_replication.html https://hbase.apache.org/book.html#_cluster_replication https://www.ngdata.com/the-hbase-side-effect-processor-and-hbase-replication-monitoring/ JMS 2017-01-17 3:42 GMT-05:00 Manjeet Singh <[email protected]>: > Hi All > > can any buddy tell why Hbase indexer required REPLICATION_SCOPE => '1' ? > > what its impact on cluster? does it take extra space? whats its internal > working? > > > - https://in.linkedin.com/in/manjeet-singh-b32023a > <https://www.linkedin.com/public-profile/settings?trk= > prof-edit-edit-public_profile> > > > Thanks > Manjeet > > -- > luv all >
