[
https://issues.apache.org/jira/browse/ATLAS-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15484857#comment-15484857
]
Suma Shivaprasad edited comment on ATLAS-205 at 9/12/16 6:25 PM:
-----------------------------------------------------------------
Cause: Index update failures could cause inconsistencies between storage and
indexing backend since there is no two-phase commit across these system in
Titan .
User Impact : Hence users using full text search may be missing some search
results compared to the equality match searches/dsl searches performed on the
storage backend.
Workaround:
Simulate whats the current bevaiour when this happens . In such a case, we
should ideally log all the entities that resulted in index update failures to
a separate log and replay the corresponding entity updates again
was (Author: suma.shivaprasad):
User Impact :
Index update failures could cause inconsistencies between storage and indexing
backend since there is no two-phase commit across these system in Titan . Hence
users using full text search may be missing some search results compared to the
equality match searches/dsl searches performed on the storage backend.
> Handle Titan Transaction failures
> ---------------------------------
>
> Key: ATLAS-205
> URL: https://issues.apache.org/jira/browse/ATLAS-205
> Project: Atlas
> Issue Type: Task
> Reporter: Suma Shivaprasad
>
> Refer
> http://s3.thinkaurelius.com/docs/titan/0.5.4/failure-recovery.html#_transaction_failure
> for details
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
