[
https://issues.apache.org/jira/browse/GEODE-3520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nabarun updated GEODE-3520:
---------------------------
Description:
If during asynchronous index maintenance, if there is an exception, the index
is marked invalid.
This will require us to provide a user a way to determine which indexes are
valid/invalid (maybe a new column in GFSH to describe index). The query engine
would need to avoid using indexes marked as invalid.
was:
Currently if a put thread hits an Index Maintenance issue, the exception is
returned back to the putter and the cache and any indexes updated up to that
point are left in a bad state. Any callbacks that occur after index
maintenance are not fired.
Instead we should probably log the exception and mark the index as invalid.
This will require us to provide a user a way to determine which indexes are
valid/invalid (maybe a new column in GFSH to describe index). The query engine
would need to avoid using indexes marked as invalid.
> IndexMaintenanceExceptions should not affect a put
> --------------------------------------------------
>
> Key: GEODE-3520
> URL: https://issues.apache.org/jira/browse/GEODE-3520
> Project: Geode
> Issue Type: Bug
> Components: querying
> Reporter: Jason Huynh
> Assignee: Jason Huynh
>
> If during asynchronous index maintenance, if there is an exception, the index
> is marked invalid.
> This will require us to provide a user a way to determine which indexes are
> valid/invalid (maybe a new column in GFSH to describe index). The query
> engine would need to avoid using indexes marked as invalid.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
