hycdong commented on issue #895:
URL: 
https://github.com/apache/incubator-pegasus/issues/895#issuecomment-1022075907


   > > Thanks for your report~ I have some problems with your cases:
   > > 
   > > * Table have one partition, and how many replicas of it? 1 replica or 3 
replicas (by default) ?
   > > * How many replica server nodes in your case?
   > > 
   > > Expecting your answer.
   > 
   > * i am sorry, the description is wrong, I have modified it, it is 1 
replica table, partition num is random, i have tested on 1 and 3 replica server 
nodes;
   > * only one replica table have this problem;
   
   Thanks for your answer, I got your case.
   
   I suppose your table has 4 partitions with only 1 replica, the stopped 
replica server called `serverA`, the data directory you delete is 
`replica/reps/1.0.pegasus`.
   - After you stop serverA, and delete serverA directory 
'replica/reps/1.0.pegasus', meta server noticed partition 1.0 can not be found 
in serverA, it will wait for serverA alive.
   - Restart serverA, meta server noticed it, then tried to recover partition 
1.0 on serverA, then create directory `replica/reps/1.0.pegasus`.
   
   As a result, the directory will be created, and this table only have one 
replica, as you directly deleted the data(in `replica/reps/1.0.pegasus`), its 
data won't exist. In multi-replica cases, it will learn data from other 
replicas.
   I think it is not bug, in your case, data is lost and metadata are still 
stored in meta server and zk, meta server will recreate directory but can not 
recover the data.
   Hoping my answer is helpful, expecting your reply~


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to