Views should provide pending, online, offline states similar to 2i

From: Cihan Biyikoglu <cihan@couchbase.com>
Subject: Re: index status when building view indexes

Thanks appreciate the details.
I am sure folks will correct me if I am wrong here but The index definition of the online is the index exists (not rebalanced out) and has reached the timestamp of creation. MR Views don't provide a way for this and tasks cannot be used for the same purpose.
Given this we should report MR views are online as long as they exist and is up-to-dateness is controlled by the consistency flags and all views should report. We can log an improvement for future to track this better in MR views if we are all ok with this proposal.
Thanks
-cihan

From: Gerald Sangudi <Gerald@couchbase.com>
Date: Thursday, March 5, 2015 at 3:18 PM
Subject: Re: index status when building view indexes

Hi Cihan,

If you issue a CREATE INDEX USING VIEW in one thread or client, and then issue a SELECT in a second thread or client, the second thread or client needs to know if the view has finished building and is ready for use, i.e. is it in a state of ONLINE, PENDING, or OFFLINE.

Thanks,
Gerald

From: Cihan Biyikoglu <cihan@couchbase.com>
Date: Thursday, March 5, 2015 at 2:42 PM
Subject: Re: index status when building view indexes

Hi folks, how do you use the status field for indexing in queries?
Thanks
-cihan

From: Gerald Sangudi <Gerald@couchbase.com>
Date: Thursday, March 5, 2015 at 12:55 PM
Subject: Re: index status when building view indexes

Thanks Siri and Volker.

I think this becomes a PM issue, based on a technical recommendation from Manik.

Thanks,
Gerald

On Mar 5, 2015 12:49 PM, Volker Mische <volker@couchbase.com> wrote:
Hi Gerald,

if I understand you correctly, you'd like to know the indexing progress.
You an use `/pools/default/tasks` for that.

Cheers,
Volker

On 03/05/2015 08:33 PM, Sriram Melkote wrote:
> Hi Gerald,
>
> In views, there's no central coordinator. Each node is building a
> subsection of the view on its own, so there's no good way for any one
> node to know what's happening elsewhere.
>
> It is possible is for one node to reach out to all others and check
> their status, and repeat periodically. This is pretty much already
> accomplished by issuing a stale=false query and waiting for a successful
> response. That'd indicate the view is online.
>
> The other place is in ns_server. As ns_server is coordinating the index
> building, it may be possible to assemble a global view there. Though I'm
> not sure if it'll be any more robust than issuing a stale=false query.
> I've also tried to follow view build using ns_server /tasks API and
> hadn't got very far with it.
>
> Looping in view folks for more details.
>
> Thanks,
> Siri
>
>
> From: Gerald Sangudi <Gerald@couchbase.com <Gerald@couchbase.com>>
> Date: Wednesday, March 4, 2015 at 11:42 PM
> To: Admin <siri@couchbase.com <siri@couchbase.com>>, Sarath
> Lakshman <sarath@couchbase.com <sarath@couchbase.com>>
> Cc: Dave Finlay <dave.finlay@couchbase.com
> <dave.finlay@couchbase.com>>, Keshav Murthy <keshav@couchbase.com
> <keshav@couchbase.com>>, Cihan Biyikoglu <cihan@couchbase.com
> <cihan@couchbase.com>>, Manik Taneja <manik@couchbase.com
> <manik@couchbase.com>>
> Subject: index status when building view indexes
>
> Hi Siri,
>
> There is a gap which has been exposed by QE.
>
> We added index status for GSI indexes, with ONLINE / PENDING / OFFLINE.
>
> The same status capability is not available for view indexes; this
> affects users when they create a view index on a large dataset, and the
> system:indexes shows ONLINE status while the view index is still being
> built.
>
> The following bugs are related to this:
>
> MB-13678 <https://issues.couchbase.com/browse/MB-13678>
> MB-13677 <https://issues.couchbase.com/browse/MB-13677>
> MB-13676 <https://issues.couchbase.com/browse/MB-13676>
>
> What is the feasibility of addressing this? Should we meet to discuss?
>
> Thanks,
> Gerald