I double checked one piece of the above log of the "ALL" mode kylin
instance:

17:36:21,910][INFO][org.apache.kylin.common.restclient.Broadcaster$1.run(Broadcaster.java:71)]
- new broadcast event:BroadcastEvent{type=cube, name=lbs_ma
p_new_user_fact, action=update}
2553 [pool-7-thread-10]:[2015-05-06
17:36:21,911][DEBUG][org.apache.kylin.common.persistence.ResourceStore.putResource(ResourceStore.java:171)]
- Saving resource /execute_output/f03d3c3c-68
f4-4593-b01d-2778fcaf098b-15 (Store kylin_metadata@hbase)
2554 [pool-7-thread-10]:[2015-05-06
17:36:21,921][DEBUG][org.apache.kylin.common.persistence.ResourceStore.putResource(ResourceStore.java:171)]
- Saving resource /execute_output/f03d3c3c-68
f4-4593-b01d-2778fcaf098b-15 (Store kylin_metadata@hbase)
2555 [http-bio-8081-exec-5]:[2015-05-06
17:36:21,922][INFO][org.apache.kylin.rest.controller.CacheController.wipeCache(CacheController.java:63)]
- wipe cache type: CUBE event:UPDATE name:lb     s_map_new_user_fact


from the first line and the last line, it seems that it tries to call sync
something related to 'rest',  however, when I check the kylin.log for each
of the "QUERY" mode kylin instances, no related log reponse to the rest sync

Reply via email to