[ 
https://issues.apache.org/jira/browse/KYLIN-5460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ruixuan Zhang updated KYLIN-5460:
---------------------------------
    Description: When resource group is turned on, using EnhancedUnitOfWork to 
write metadata will check if current owner has the write permission, that is, 
whether the node is in the build resource group. The new feature of providing 
more flexible runtime join will force KYLIN to go into maintenance mode when 
using script to update and write metadata, this will have mocked node IP:0000 
owning the epoch and since the mocked node is not in the build resource group, 
it will cause write failure.  (was: When resource group is turned on, using 
EnhancedUnitOfWork to write metadata will check if current owner has the write 
permission, that is, if the node is in the build resource group. The new 
feature of providing more flexible runtime join will force KYLIN to go into 
maintenance mode when using script to update and write metadata, this will have 
mocked node IP:0000 occupy the epoch and since the mocked node is not in the 
build resource group, which causes write failure.)

> When resource group is turned on, using EnhancedUnitOfWork to write metadata 
> might fail
> ---------------------------------------------------------------------------------------
>
>                 Key: KYLIN-5460
>                 URL: https://issues.apache.org/jira/browse/KYLIN-5460
>             Project: Kylin
>          Issue Type: Improvement
>          Components: Metadata
>    Affects Versions: 5.0-alpha
>            Reporter: Ruixuan Zhang
>            Assignee: Ruixuan Zhang
>            Priority: Major
>             Fix For: 5.0-alpha
>
>
> When resource group is turned on, using EnhancedUnitOfWork to write metadata 
> will check if current owner has the write permission, that is, whether the 
> node is in the build resource group. The new feature of providing more 
> flexible runtime join will force KYLIN to go into maintenance mode when using 
> script to update and write metadata, this will have mocked node IP:0000 
> owning the epoch and since the mocked node is not in the build resource 
> group, it will cause write failure.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to