Bug 1028456 - Too many session timeout during read repair
Too many session timeout during read repair
Status: NEW
Product: RHQ Project
Classification: Other
Component: Installer (Show other bugs)
4.9
x86_64 All
unspecified Severity low (vote)
: ---
: ---
Assigned To: RHQ Project Maintainer
Mike Foley
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-11-08 08:39 EST by Armine Hovsepyan
Modified: 2015-09-02 20:04 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
rhq-storage.log (1.31 MB, text/x-log)
2013-11-08 08:39 EST, Armine Hovsepyan
no flags Details

  None (edit)
Description Armine Hovsepyan 2013-11-08 08:39:51 EST
Created attachment 821618 [details]
rhq-storage.log

Description of problem:
Too many session timeout during read repair 

Version-Release number of selected component (if applicable):
rhq 4.10 master id: d3ea23b

How reproducible:
3 out of 6

Steps to Reproduce:
1. install rhq server, storage and agent on IP1
2. install storage and agent on IP2, connect to IP1
3. make announce of IP2 for IP1 fail
4. install storage and agent on IP3, connect to IP1
5. start storage in IP3 

Actual results:
The following exception is viisble in log very often:

ERROR [RMI TCP Connection(179)-127.0.0.1] 2013-11-08 08:25:50,150 StorageService.java (line 2448) Repair session failed:
java.lang.IllegalArgumentException: Requested range intersects a local range but is not fully contained in one; this would lead to imprecise repair

Expected results:
No timeout exception in rhq-storage.log or a catched exception, if existing one is not problematic 

Additional info:
full rhq-storage.log attached

The presence of bug doesn't block read repair process and at the end of the process full data repair takes part, thus marking the bug as minor.

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