Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1300987

Summary:	Accumulo translator doesn't end query execution when there are no tablet servers
Product:	[JBoss] JBoss Data Virtualization 6	Reporter:	Jan Stastny <jstastny>
Component:	Teiid	Assignee:	Van Halbert <vhalbert>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Jan Stastny <jstastny>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.3.0	CC:	aszczucz, blafond, ctubbsii, jolee, mbaluch, thauser, vhalbert
Target Milestone:	ER1
Target Release:	6.3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-08-24 11:46:11 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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