On Thu, 03 May 2012 12:16:06 +0200, Vijay Bellur <[email protected]>
wrote:
On 05/03/2012 03:44 PM, Geoff Galitz wrote:
I then ran the command:
gluster volume heal testvol
After I ran that, there was some activity, and now all the files were
populated.
Was that supposed to happen automatically, eventually, or am I
missing something about how the self-heal daemon works?
The self-heal daemon triggers a crawl once every 600 seconds. If you
wait out that interval, you should be able to see self-heals happening
automatically. Else you can trigger it explicitly the way you did.
As a follow-up question to that: does this all apply to gluster 3.2.4
also? And if you manually trigger a self-heal (via doing a find + stat
as some of us were originally trained) multiple times within a 10
minute window, will that cause a problem?
This does not apply to gluster 3.2.4. Manually triggering a self-heal
multiple times should not cause a problem. If you notice any aberration,
please do let us know.
It is just that we had an issue where we had a two brick configuration go
suddenly out-of-sync a few times and running a heal didn't seem to solve
it. A number of files showed as zero length which, to our understanding,
means gluster determined they were problematic. We had to remove one of
the bricks and were never able to get it fully synced up again. We took
it out of service, populated it via rsync and then put it back. Later it
broke again but a self-heal did solve it.
----
Geoff Galitz, [email protected]
WebOps Engineer, Europe
Shutterstock Images
http://wwww.shutterstock.com/
_______________________________________________
Gluster-users mailing list
[email protected]
http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
