Bug 1300987 - Accumulo translator doesn't end query execution when there are no tablet servers
Summary: Accumulo translator doesn't end query execution when there are no tablet servers
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Data Virtualization 6
Classification: JBoss
Component: Teiid
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ER1
: 6.3.0
Assignee: Van Halbert
QA Contact: Jan Stastny
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-22 09:44 UTC by Jan Stastny
Modified: 2016-08-24 11:46 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-24 11:46:11 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker TEIID-3921 0 Major Resolved Accumulo translator doesn't end query execution when there are no tablet servers 2016-06-08 11:32:19 UTC

Description Jan Stastny 2016-01-22 09:44:46 UTC
Description of problem:
When querying an Accumulo instance using accumulo translator, there is a problem with running queries against an instance, which is not running. The query is running until query timeout exceeds.
More information in linked TEIID-3921.


Version:
DV 6.3.0 DR1

Comment 1 Christopher Tubbs 2016-01-25 00:40:41 UTC
It sounds like you're describing the expected/designed behavior of Accumulo. Accumulo is designed to migrate data between tablet servers when servers go offline and come online. The Accumulo client code should continue retrying until it reaches some client-side timeout.

I'm not familiar with "Teiid Accumulo translator" but as a developer on Accumulo upstream, I think you're describing normal, expected, and desired behavior. Am I missing something?

Comment 2 JBoss JIRA Server 2016-01-29 16:44:02 UTC
Ramesh Reddy <rareddy> updated the status of jira TEIID-3921 to Coding In Progress

Comment 3 JBoss JIRA Server 2016-01-30 19:50:54 UTC
Ramesh Reddy <rareddy> updated the status of jira TEIID-3921 to Resolved


Note You need to log in before you can comment on or make changes to this bug.