Couchbase

  • Log In Access more options
    • Online Help
    • GreenHopper Help
    • Agile Answers
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What’s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
  • Agile Access more options (Alt+g)
  • Couchbase.com Access more options
    • Why NoSQL?
    • Couchbase Server
    • Download
    • Learn
    • Careers
Couchbase C client library libcouchbase
  • Couchbase C client library libcouchbase
  • CCBC-174

Error handling documentation

  • Agile Board
  • More Actions
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Improvement Improvement
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 2.0.2
  • Fix Version/s: None
  • Component/s: docs
  • Security Level: Public
  • Labels:
    None

Description

Please create some documentation specifying possible error/failures to operations, what they "look" like in the logs/exceptions/stack traces and what our recommendation is on how to handle them.

i.e. tmp_oom, timeouts (connection/operation/java-internal/etc), "get miss" (it's technically a failure, let's make it overly obvious what it means), CAS failure, add() failure, replace() failure,

Some of this should be covered in the API reference, but this bug is specifically for a single page where this information is aggregated that a customer/user could read about how to handle errors.

Activity

  • All
  • Comments
  • Work Log
  • History
  • Activity
  • Gerrit Reviews
There are no comments yet on this issue.

People

  • Assignee:
    Sergey Avseyev
    Reporter:
    Perry Krug
Vote (0)
Watch (1)

Dates

  • Created:
    05/Feb/13 2:39 AM
    Updated:
    05/Feb/13 2:39 AM

Agile

  • View on Board
  • Atlassian JIRA (v5.2.4#845-sha1:c9f4cc4)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for Couchbase. Try JIRA - bug tracking software for your team.