accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <>
Subject [jira] [Created] (ACCUMULO-1940) Data file in !METADATA differs from in memory data
Date Wed, 27 Nov 2013 15:26:36 GMT
Josh Elser created ACCUMULO-1940:

             Summary: Data file in !METADATA differs from in memory data
                 Key: ACCUMULO-1940
             Project: Accumulo
          Issue Type: Bug
          Components: test
    Affects Versions: 1.5.0
            Reporter: Josh Elser

Found during CI run with agitation.

Got the first two error messages 5 times (assuming in a retry on failure block):

Failed to do close consistency check for tablet c;79d0ab;7870a
	java.lang.RuntimeException: Data file in !METADATA differ from in memory data c;79d0ab;7870a
 {/t-0005h1j/A0005n8k.rf=797350457 19198312, /t-0005h1j/C0005skm.rf=798078368 19322025, /t-0005h1j/C0005tet.rf=89783168
2196349, /t-0005h1j/C0005u20.rf=90979448 2227972, /t-0005h1j/F0005u0v.rf=23410023 582233,
/t-0005h1j/F0005u2p.rf=21958551 547159, /t-0005h1j/F0005u3g.rf=14395121 358893}  {/t-0005h1j/A0005n8k.rf=797350457
19198312, /t-0005h1j/C0005skm.rf=798078368 19322025, /t-0005h1j/C0005tet.rf=89783168 2196349,
/t-0005h1j/C0005u20.rf=90979448 2227972, /t-0005h1j/F0005u2p.rf=21958551 547159, /t-0005h1j/F0005u3g.rf=14395121
		at org.apache.accumulo.server.tabletserver.Tablet.closeConsistencyCheck(
		at org.apache.accumulo.server.tabletserver.Tablet.completeClose(
		at org.apache.accumulo.server.tabletserver.Tablet.close(
		at org.apache.accumulo.server.tabletserver.TabletServer$
		at java.util.concurrent.ThreadPoolExecutor.runWorker(
		at java.util.concurrent.ThreadPoolExecutor$

Then, we logged that we failed the consistency check

Consistency check fails, retrying java.lang.RuntimeException: Failed to do close consistency
check for tablet c;79d0ab;7870a

In the end, we gave up and closed it anyways.

Tablet closed consistency check has failed for c;79d0ab;7870a giving up and closing

This left me with some table problems, but everything appears to be working fine at the moment.
Not sure if something was lost silently (until I shut down and run a verify), but it certainly
looks ominous.

This message was sent by Atlassian JIRA

View raw message