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 Server
  • Couchbase Server
  • MB-7614

XDCR observe

  • 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
  • Fix Version/s: .next
  • Component/s: couchbase-bucket, cross-datacenter-replication
  • Security Level: Public
  • Labels:
    None
  • Environment:
    Couchbase Server 2.0 GA with XDCR either across datacenters or AWS Regions

Description

Add functionality on the Couchbase server side so that a client level request for observe can block the request until either persisted to disk, replicated to another node intra cluster or replicated to a remote cluster.

Issue Links

blocks

Improvement - An improvement or enhancement to an existing feature or task. JCBC-221 XDCR observe - java client

  • Major - Major loss of function.
  • Open - The issue is open and ready for the assignee to start work on it.

Activity

Ascending order - Click to sort in descending order
  • All
  • Comments
  • Work Log
  • History
  • Activity
  • Gerrit Reviews
Hide
Permalink
Dipti Borkar added a comment - 31/Jan/13 1:46 AM
please add more requirements to this bug as they are available. we have not yet planned to implement this until more discussion happens.
Show
Dipti Borkar added a comment - 31/Jan/13 1:46 AM please add more requirements to this bug as they are available. we have not yet planned to implement this until more discussion happens.
Hide
Permalink
Perry Krug added a comment - 31/Jan/13 3:40 AM
I think it's very simply that a user wants to be able to know when a particular revision of an item has been received by the XDCR bucket on another cluster. It gets a little more complicated with multiple outgoing streams, but would be critical for ensuring actual consistency across clusters.
Show
Perry Krug added a comment - 31/Jan/13 3:40 AM I think it's very simply that a user wants to be able to know when a particular revision of an item has been received by the XDCR bucket on another cluster. It gets a little more complicated with multiple outgoing streams, but would be critical for ensuring actual consistency across clusters.

People

  • Assignee:
    Dipti Borkar
    Reporter:
    Alex Ma
Vote (2)
Watch (2)

Dates

  • Created:
    28/Jan/13 12:25 PM
    Updated:
    20/Feb/13 12:18 PM

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.