Hello Ketan

If the merge is not triggered, there should be some logs saying why
the merge is ignored. That log is not exception or warn, but INFO you
what the system is expecting to do.

With Warm regards

Billy Liu


2018-04-10 15:34 GMT+08:00 ketan dikshit <kdcool6...@yahoo.com.invalid>:
> Hi Team,
> I am working with Kylin 2.3.1 for last few days, have seen that Kylin 
> auto-merge functionality is not working.
> I have not set the volatile range(default=0), so should be default behaviour.
>
> Also not able to see any error in logs as well. So basically its not being 
> triggered.
> Here is the commit_sha ID: 1e322992b8011d3b430321599d6da762c1a5e6b9
>
> Could you please point me how to debug or resolve the same, what could be the 
> potential errors/blockers in here ?
>
> And Here are my kylin.properties,(nothing special here)
>
> kylin.web.timezone=US/Pacific
> kylin.metadata.url=kylin2.3.1Meta@hbase
> kylin.storage.url=hbase
> kylin.env.hdfs-working-dir=/tmp/kylin-2.3.1-DEV
> kylin.engine.mr.reduce-input-mb=300
> kylin.server.mode=all
> kylin.env=TEST
> kylin.job.max-concurrent-jobs=10
> kylin.engine.mr.yarn-check-interval-seconds=10
> kylin.storage.hbase.table-name-prefix=KYL_TEST_
> kylin.source.hive.database-for-flat-table=kylin
> kylin.storage.hbase.compression-codec=lz4
> kylin.storage.hbase.region-cut-gb=3
> kylin.storage.hbase.min-region-count=1
> kylin.storage.hbase.max-region-count=5000
> kylin.storage.partition.max-scan-bytes=16106127360
> kylin.storage.hbase.coprocessor-mem-gb=6
> kylin.security.profile=testing
> kylin.query.cache-enabled=true
> kylin.query.cache-threshold-duration=500
> kylin.query.cache-threshold-scan-count=10240
> kylin.storage.hbase.scan-cache-rows=4096
>
> Any help would be appreciated.
>
> Thanks,
> Ketan@Exponential
>
>

Reply via email to