{"action":"opened","issue":{"url":"https://api.github.com/repos/basho/yokozuna/issues/494","labels_url":"https://api.github.com/repos/basho/yokozuna/issues/494/labels{/name}","comments_url":"https://api.github.com/repos/basho/yokozuna/issues/494/comments","events_url":"https://api.github.com/repos/basho/yokozuna/issues/494/events","html_url":"https://github.com/basho/yokozuna/issues/494","id":80855653,"number":494,"title":"Avoid serving search requests by re-assigned vnodes until (AAE) re-indexing completes","user":{"login":"binarytemple","id":419046,"avatar_url":"https://avatars.githubusercontent.com/u/419046?v=3","gravatar_id":"","url":"https://api.github.com/users/binarytemple","html_url":"https://github.com/binarytemple","followers_url":"https://api.github.com/users/binarytemple/followers","following_url":"https://api.github.com/users/binarytemple/following{/other_user}","gists_url":"https://api.github.com/users/binarytemple/gists{/gist_id}","starred_url":"https://api.github.com/users/binarytemple/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/binarytemple/subscriptions","organizations_url":"https://api.github.com/users/binarytemple/orgs","repos_url":"https://api.github.com/users/binarytemple/repos","events_url":"https://api.github.com/users/binarytemple/events{/privacy}","received_events_url":"https://api.github.com/users/binarytemple/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-05-26T08:24:04Z","updated_at":"2015-05-26T08:24:04Z","closed_at":null,"body":"[Customer request](https://basho.zendesk.com/agent/tickets/10795)\r\n\r\nObservation: During process of re-indexing vnodes, search results are inconsistent.\r\n\r\n>>The problem is that unlike store/fetch, Solr search becomes inconsistent not because the keys are unavailable, but because Solr indexing is lagging behind the Riak storage. Being aware of this problem, wouldn't it make sense to avoid serving search requests by re-assigned vnodes until the indexing completes? \r\n\r\n>>To my understanding, even increasing AAE concurrency levels does not solve the problem completely. \r\n\r\nIncreasing AAE concurrency/more aggressive speeds up re-indexing, but search results will fluctuate until the process completes.\r\n\r\n"}}