Couchbase
  • Why NoSQL?
  • Couchbase Server
  • Download
  • Resources
  • Careers
Home | Forums | Couchbase | Couchbase Server 1.8.x

Intermittent Node Failure Events Using .NET Client

1 reply [Last post]
  • Login or register to post comments
Mon, 07/09/2012 - 21:29
mizuniadmin
Offline
Joined: 05/30/2012
Groups: None

We are experiencing a intermittent case when using the Couchbase .NET client connecting to a 3-node Couchbase 1.8 cluster. At completely random times, our web application will hang from 30 to 90 seconds and then run like normal for the next hour or so before hitting another 30 to 90 seconds of hanging state. We debugged the issue by attaching logs to the Couchbase events and during the hangs, we are seeing node failure events from each of the three nodes. We will random see 1 to 3 errors per node which we believe corresponds to the 30 to 90 seconds that our application is hanging.

There is a firewall between the web servers (Windows 2008R2/IIS 7.0/MVC 3.5 web application) and we have opened up ports 8091, 11210 and 11211 per the node to client documentation at http://www.couchbase.com/docs/couchbase-manual-1.8/couchbase-network-por... and http://www.couchbase.com/docs/couchbase-manual-1.8/couchbase-bestpractic.... I do not believe we need port 11210 opened up but we figured we would open that up to see if that was causing the issues. We have looked at the firewall logs and do not believe we are blocking any traffic or ports that Couchbase needs.

Has anyone in the community seen this behavior. We have a 3-node cluster in our QA environment but we do not have a firewall between our web applications and the Couchbase cluster. We are wondering if we are missing a management or heartbeat port of sometime and causing the random node failure events.

Top
  • Login or register to post comments
Mon, 07/09/2012 - 23:17
mizuniadmin
Offline
Joined: 05/30/2012
Groups: None

Sorry, a couple more items to further clarify what we are experiencing. First, we have replicated this behavior from four seperate web servers. Also, during the hanging we are able to connect to the Couchbase web console on port 8091 from the web server experiencing the hang. In fact, during one hang we were able to browse all three node cluster web consoles as normal during the hang.

I just finished reading the 1.8.1 release notes, but I didn't see anything in there that addressed connection issues.

Top
  • Login or register to post comments
  • Login or register to post comments
  • Login
  • Register

Company

  • About Us
  • Leadership
  • Customers
  • Partners
  • Contact Us

Product

  • Couchbase Server
  • Couchbase SDKs
  • Use Cases
  • Documentation
  • Forums

Open Source

  • Couchbase Project
  • Couchbase vs. CouchDB

Commercial

  • Subscriptions & Support
  • Training & Services

News

  • Blog
  • Newsletter
  • Press Releases
  • Buzz

Follow Us

    
  • Customer Login
  • Terms of Service
  • Privacy Policy
  • Trademark Policy
  • Site Map

© 2013 COUCHBASE All rights reserved.

Sign in to Couchbase Community

close
  • Create new account
  • Request new password
You are logging into the Forums, Wiki and Issue Tracker