Hi,
I am using Kylin 2.2, where I have several OLAP cubes in which I am constantly adding and refreshing segments. I am faced with a problem that has generated two segments for the same period of time and therefore an error of the "segments overlap" type. Kylin is also cluster mounted, with one machine for cube building and one for querying. Here is the log of the query machine that seems to reflect the error (cube segment building process was successfully completed): 2018-08-16 09:19:35,833 INFO [http-bio-7070-exec-93] cube.CubeManager:799 : Reloaded cube trafico_cubo_v8 being CUBE[name=trafico_cubo_v8] having 20 segments 2018-08-16 09:19:35,833 DEBUG [http-bio-7070-exec-93] cachesync.Broadcaster:256 : BroadcastingUPDATE, project_data, My_Cube_Trafico 2018-08-16 09:19:35,834 INFO [http-bio-7070-exec-93] service.CacheService:143 : removeOLAPDataSource is called for project My_Cube_Trafico 2018-08-16 09:19:35,834 INFO [http-bio-7070-exec-93] service.CacheService:125 : cleaning cache for project My_Cube_Trafico (currently remove all entries) 2018-08-16 09:19:35,834 DEBUG [http-bio-7070-exec-93] cachesync.Broadcaster:290 : Done broadcastingUPDATE, project_data, My_Cube_Trafico 2018-08-16 09:19:35,834 DEBUG [http-bio-7070-exec-93] cachesync.Broadcaster:290 : Done broadcastingUPDATE, cube, trafico_cubo_v8 2018-08-16 09:19:36,817 INFO [http-bio-7070-exec-104] cube.CubeManager:358 : Updating cube instance 'plataforma_cubo_mes_v2' 2018-08-16 09:19:36,817 ERROR [http-bio-7070-exec-104] controller.CubeController:337 : Segments overlap: plataforma_cubo_mes_v2[20180801000000_20180901000000] and plataforma_cubo_mes_v2[20180801000000_20180901000000] 2018-08-16 09:19:36,818 ERROR [http-bio-7070-exec-104] controller.BasicController:57 : 2018-08-16 09:19:37,264 DEBUG [http-bio-7070-exec-93] cachesync.Broadcaster:256 : BroadcastingUPDATE, cube, trafico_cubo_v8 2018-08-16 09:19:37,265 INFO [http-bio-7070-exec-93] cube.CubeManager:799 : Reloaded cube trafico_cubo_v8 being CUBE[name=trafico_cubo_v8] having 20 segments Could this error be related to the JIRA entry https://issues.apache.org/jira/browse/KYLIN-3311? In that case, I see that it has been fixed in version 2.4 of Kylin. Also, to fix the error, we had to stop Kylin, remove the duplicate segment from the metadata, restart Kylin and then refresh the segment. As far as I can read on the website https://issues.apache.org/jira/browse/KYLIN-2849 , from version 2.3 onwards you can delete a segment in any position from the UI or the Kylin API after disabling the cube. Is that correct? This would help us mitigate the problem more quickly. Thanks in advance! Roberto TardÃo Olmos Head of Big Data Analytics Avenida de Brasil, 17, Planta 16.28020 Madrid Fijo: 91.788.34.10 http://bigdata.stratebi.com/ http://www.stratebi.com <http://www.stratebi.com/>
