[MB-4848] possible active/replica index optimizations Created: 28/Feb/12  Updated: 10/Jan/13  Resolved: 01/Mar/12

Status: Closed
Project: Couchbase Server
Component/s: ns_server
Affects Version/s: 2.0-developer-preview-4
Fix Version/s: 2.0
Security Level: Public

Type: Improvement Priority: Major
Reporter: Tommie McAfee Assignee: Filipe Manana
Resolution: Fixed Votes: 0
Labels: 2.0-dev-preview-4-release-notes
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment: dp4 717


 Description   
Given (MB-4847) and its impact on the user .... Couchbase itself could try to avoid this scenario by prioritizing some active threads before replica or allowing user to set a % for how many active/replica threads should be running at any given time.

 Comments   
Comment by Filipe Manana [ 01/Mar/12 ]
Applied to master branch:

https://github.com/couchbase/couchdb/commit/4812813fddb9255bc7c31f258e54803273120dd7

Main indexers get 4 exclusive slots and replica indexes 2 exclusive slots by default
Generated at Sun Jul 13 16:30:11 CDT 2014 using JIRA 5.2.4#845-sha1:c9f4cc41abe72fb236945343a1f485c2c844dac9.