[
https://issues.apache.org/jira/browse/HBASE-16255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15451197#comment-15451197
]
Devaraj Das edited comment on HBASE-16255 at 8/31/16 5:33 AM:
--------------------------------------------------------------
Ah I think the issue is that in the docker env, all the hbase processes run as
'root', and hence the backup dirs end up being created as 'root'. But at some
point in the sanpshot copy or something, the user switches to hbase and fails
to perform the filesystem operations.
I bet if things are run as 'hbase' things will work. [~dspivak] can you please
check the docker stuff to run the server processes in the more natural
deployment style - hbase regionserver processes as hbase, etc..
was (Author: devaraj):
Ah I think the issue is that in the docker env, all the hbase processes run as
'root', and hence the backup dirs end up being created as 'root'. But at some
point in the sanpshot copy or something, the user switches to hbase and fails
to perform the filesystem operations.
I bet if things are run as 'hbase' things will work. [~dspivak] can you please
check the docker stuff to run the processes in the more natural deployment
style - hbase processes as hbase, etc..
> Backup/Restore IT
> -----------------
>
> Key: HBASE-16255
> URL: https://issues.apache.org/jira/browse/HBASE-16255
> Project: HBase
> Issue Type: Task
> Reporter: Vladimir Rodionov
> Assignee: Vladimir Rodionov
> Labels: backup
> Attachments: 16255-addendum.3.txt, 16255.addendum, 16255.addendum2,
> 16255.addendum4, 16255.addendum5, 16255.addendum6, HBASE-16255-v1.patch,
> HBASE-16255-v2.patch, HBASE-16255-v3.patch, HBASE-16255-v4.patch,
> HBASE-16255-v5.patch, HBASE-16255-v6.patch, backup-it-7912-8-30.out,
> backup-it-8-30.out, backup-it-success.out
>
>
> Integration test for backup restore.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
