Bug 764049 (GLUSTER-2317) - how to migrate a client-server configuration
Summary: how to migrate a client-server configuration
Keywords:
Status: CLOSED WORKSFORME
Alias: GLUSTER-2317
Product: GlusterFS
Classification: Community
Component: core
Version: 3.1.2
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Anand Avati
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-25 10:32 UTC by Eatdirt
Modified: 2015-09-01 23:05 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: fuse
Documentation: ---
CRM:
Verified Versions:


Attachments (Terms of Use)

Description Eatdirt 2011-01-25 10:32:35 UTC
Hi,
after having read the documentation and the migration pages; there is no reference on how to migrate a client-server configuration 3.0.4 to the new 3.1.2.

As far as I can read, I cannot use the old volume file configuration. Anyway I tried, and glusterfs segfaults.

My old config files on 13 nodes are recap below, they were simple, efficient, and I clearly do not intent to reconfigure my whole cluster; so I hope I can import them in a easy way; which does not seem to be the case right now.

Chris.

---- example


volume client-02
 type protocol/client
 option transport-type tcp/client
 option remote-host mercury
 option remote-subvolume brick
end-volume

volume client-03
 type protocol/client
 option transport-type tcp/client
 option remote-host venus
 option remote-subvolume brick
end-volume

volume client-04
 type protocol/client
 option transport-type tcp/client
 option remote-host earth
 option remote-subvolume brick
end-volume

volume client-05
 type protocol/client
 option transport-type tcp/client
 option remote-host mars
 option remote-subvolume brick
end-volume

volume client-06
 type protocol/client
 option transport-type tcp/client
 option remote-host jupiter
 option remote-subvolume brick
end-volume

volume client-07
 type protocol/client
 option transport-type tcp/client
 option remote-host saturn
 option remote-subvolume brick
end-volume

volume client-08
 type protocol/client
 option transport-type tcp/client
 option remote-host uranus
 option remote-subvolume brick
end-volume

volume client-09
 type protocol/client
 option transport-type tcp/client
 option remote-host neptune
 option remote-subvolume brick
end-volume

volume client-10
 type protocol/client
 option transport-type tcp/client
 option remote-host pluto
 option remote-subvolume brick
end-volume

volume client-11
 type protocol/client
 option transport-type tcp/client
 option remote-host haumea
 option remote-subvolume brick
end-volume

volume client-12
 type protocol/client
 option transport-type tcp/client
 option remote-host makemake
 option remote-subvolume brick
end-volume

volume client-13
 type protocol/client
 option transport-type tcp/client
 option remote-host eris
 option remote-subvolume brick
end-volume

volume unify
 type cluster/distribute
 option lookup-unhashed yes
 option min-free-disk 5%
 subvolumes client-02 client-03 client-04 client-05 client-06 client-07 client-08 client-09 client-10 client-11 client-12 client-13
end-volume

volume unify-iot
  type performance/io-threads
  option thread-count 16
  subvolumes unify
end-volume

volume unify-wbd
  type performance/write-behind
  subvolumes unify-iot
end-volume

volume unify-ioc
  type performance/io-cache
  option cache-size 1024MB
  subvolumes unify-wbd
end-volume

Comment 1 Anand Avati 2011-01-26 03:25:46 UTC
(In reply to comment #0)
> Hi,
> after having read the documentation and the migration pages; there is no
> reference on how to migrate a client-server configuration 3.0.4 to the new
> 3.1.2.
> 
> As far as I can read, I cannot use the old volume file configuration. Anyway I
> tried, and glusterfs segfaults.
> 
> My old config files on 13 nodes are recap below, they were simple, efficient,
> and I clearly do not intent to reconfigure my whole cluster; so I hope I can
> import them in a easy way; which does not seem to be the case right now.
> 
> Chris.


Can you post the backtrace of your segfault? If you tried to use the same volfile and start glusterfsd and glusterfs client (without using glusterd/gluster cli) it should still work in theory. I'm interested to see what caused the segfault.

Avati

Comment 2 Amar Tumballi 2011-07-15 06:13:56 UTC
Bug timeout.

We have clear documentation about migration now in our wiki.


Note You need to log in before you can comment on or make changes to this bug.