bugGluster - Bugs: bug #26462, dns failure causing...

 
 

bug #26462: dns failure causing "Transport endpoint is not connected"

Submitted by:  Erick Tryzelaar <erickt>
Submitted on:  Wed 06 May 2009 12:00:39 AM UTC  
 
Category: GlusterFSSeverity: 3 - Normal
Priority: 5 - NormalItem Group: Improper behaviour
Status: PostponedPrivacy: Public
Assigned to: NoneOriginator Name: Erick
Open/Closed: ClosedRelease: 2.0.0
Operating System: GNU/LinuxReproducibility: Every Time

Add a New Comment(Rich Markup)
   

You are not logged in

Please log in, so followups can be emailed to you.

 

Thu 25 Jun 2009 07:10:36 AM UTC, comment #1:

This bug has been moved to http://bugs.gluster.com

Please track the progress of the bug at http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=71

--
Gowda

Basavanagowda Kanur <gowda>
Project Member
Wed 06 May 2009 12:00:39 AM UTC, original submission:

We ran into a problem where one of the machines we intended to use happened to not be in our dns. When we touch a file, we get this error:

> touch /mnt/glusterfs/foo

touch: setting times of `/mnt/glusterfs/foo': Transport endpoint is not connected

This only happens when we have this specific client .vol:

volume server1
type protocol/client
option transport-type tcp
option remote-host server1
option remote-subvolume write-behind
end-volume

volume server2
type protocol/client
option transport-type tcp
option remote-host server2-does-not-exist
option remote-subvolume write-behind
end-volume

volume stripe1
type cluster/stripe
subvolumes server1 server2
end-volume

volume server3
type protocol/client
option transport-type tcp
option remote-host server3
option remote-subvolume write-behind
end-volume

volume server4
type protocol/client
option transport-type tcp
option remote-host server4
option remote-subvolume write-behind
end-volume

volume stripe2
type cluster/stripe
subvolumes server3 server4
end-volume

volume mirror
type cluster/replicate
subvolumes stripe1 stripe2
end-volume

volume distribute
type cluster/distribute
subvolumes mirror
end-volume

For completion, here's the server.vol:

volume posix
type storage/posix
option directory /tmp/gluster
end-volume

volume locks
type features/locks
subvolumes posix
end-volume

volume io-threads
type performance/io-threads
option thread-count 8
subvolumes locks
end-volume

volume read-ahead
type performance/read-ahead
option page-size 1MB
option page-count 4
subvolumes io-threads
end-volume

volume write-behind
type performance/write-behind
option aggregate-size 128KB
option window-size 1MB
subvolumes read-ahead
end-volume

volume server
type protocol/server
option transport-type tcp
option auth.addr.write-behind.allow *
subvolumes write-behind
end-volume

Anyway, if I remove any of the cluster translators, this error doesn't happen. I've attached the glusterfs.log if that helps.

Erick Tryzelaar <erickt>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach File(s):
   
   
Comment:
   

Attached Files
file #18097:  glusterfs.log added by erickt (39KiB - application/octet-stream)

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -unavailable- added by gowda (Posted a comment)
  • -unavailable- added by erickt (Submitted the item)
  •  

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    Follow 4 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Thu 25 Jun 2009 07:10:36 AM UTCgowdaStatusNone=>Postponed
      Originator Name=>Erick
      Open/ClosedOpen=>Closed
    Wed 06 May 2009 12:00:39 AM UTCericktAttached File-=>Added glusterfs.log, #18097

    Back to the top


    Powered by Savane 3.1-cleanup1