[ic] Perl 5.8.0 + Interchange Clustering locking issues

interchange-users@icdevgroup.org interchange-users@icdevgroup.org
Mon Sep 9 22:48:01 2002


On Mon, Sep 09, 2002 at 07:19:31PM -0700, Dan Browning wrote:
> At 10:01 PM 9/9/2002 -0400, you wrote:
> >On Mon, Sep 09, 2002 at 06:45:02PM -0700, Barry Treahy, Jr. wrote:
> >> Dan Browning wrote:
> >>
> >> >At 09:36 PM 9/8/2002 -0700, you wrote:
> >> >
> >> >>At 10:28 PM 7/27/2002 +0200, you wrote:
> >> >>
> >> >>>>Dan Browning wrote:
> >> >>>>
> >> >>>>>For fun, I was testing Perl 5.8.0 (default build options) on our
> >> >>>>>Interchange cluster and found some file locking problems.  We'll
> >> >>>>>be sticking with 5.6.1 for now, but I wanted to warn those who run
> >> >>>>>clusters just in case they try it:
> >> >>>>>x.x.x.x - - [27/July/2002:12:10:03 -0700] www11
> >> >>>>>/cgi-bin/template/index.html Runtime error: Could not lock file:
> >> >>>>>Interrupted system call
> >> >>>>>It occurs even under very light loads, with MySQL sessions, and
> >> >>>>>everything else shared over NFS3 (fcntl locks).  Perhaps it will
> >> >>>>>be fixed in Perl 5.8.1...
> >
> >
> >How do you know that is perl related and not NFS or NFS3?
> 
> It could be a NFS configuration problem, but here is what I know:
> 
>  * 5.6.1 works fine for our cluster (NFS)
> 
>  * Barry doesn't use NFS, neither does he have a cluster, but is
>    experiencing the same problem with 5.8.0.
> 
> >At least
> >in debian world, NFS defaults just changed to sync from async.  Perl
> >changed from unthreaded to threaded.
> 
> That was gutsy, but I guess the threading is supposed to be a lot better in 
> 5.8.x.  Of course, I've known Debian to be everything except gutsy, so...
> 
> >If you are running mysql sessions,
> >what do you have to lock?  An order counter and some log files?
> 
> tmp/*
> 
> >Why
> >do you need to lock index.html?  Couldn't it be ro FWIW?
> 
> It isn't locked, it only reports the error.  The only NFS directories are:
> 
> etc/
> orders/
> products/
> tmp/

Oh.  Silly me thinking another system looks like ours.  We have
everything but the sessions and tmp in mysql.  Interesting, I've never
looked at tmp except to clean it.  Hmmm, they are all counter files.
I suppose that could be an issue.  OTOH, if they are just counter
files, then move them into sql too.  What are these things?  They are
all just 1 on our system:
#COUNTER-1.0
1
#COUNTER-1.0
1
#COUNTER-1.0
Looks like another feature we don't use.



> 
> Everything else is sync'ed via CVS.  Of all those, tmp is the one that 
> causes the most lock contention.
> 
> >I'm confused AND about to upgrade to 5.8 on our production machines
> >ATRSN.  :-)
> 

Any Time Real Soon Now =~/almost done/;

> WDATSF? [1]  :-)
> 
> /~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\
> | Dan Browning, Kavod Technologies      <dan.browning@kavod.com> |
> | (360) 882-7872 x7, 6700 NE 162nd Ave, Suite 210, Vancouver, WA |
> \~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~/
> So, what's with this guy Gideon, anyway?  And why can't he ever
> remember his Bible?
> 
> 
> [1] What does AT Stand For
> 
> _______________________________________________
> interchange-users mailing list
> interchange-users@icdevgroup.org
> http://www.icdevgroup.org/mailman/listinfo/interchange-users
> 

-- 

Christopher F. Miller, Publisher                               cfm@maine.com
MaineStreet Communications, Inc           208 Portland Road, Gray, ME  04039
1.207.657.5078                                         http://www.maine.com/
Content/site management, online commerce, internet integration, Debian linux