accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-1653) Unable to merge during RandomWalk
Date Sat, 07 Nov 2015 18:46:11 GMT


Josh Elser commented on ACCUMULO-1653:

Actually, re-reading through the linked issues, there was no code change for a defect. The
only thing added were tests. It's possible there's another issue that happened to fix a bug,
but I'm not sure. We're happy to help you on the mailing lists with Apache Accumulo defects,
but vendor specific issues are better served on that vendor's support channels.

> Unable to merge during RandomWalk
> ---------------------------------
>                 Key: ACCUMULO-1653
>                 URL:
>             Project: Accumulo
>          Issue Type: Bug
>            Reporter: Sean Hickey
> I was running RandomWalk and ran into an issue where one of my walkers got stuck doing
a merge (on table id=20). The only related error that showed up was that a file in HDFS couldn't
be found (and continues to not be found, it keeps checking regularly) while trying to merge
the metadata records. Here's the error:
> {noformat}
> 2013-08-14 11:54:27,246 [master.Master] ERROR: Unable merge metadata table records
> org.apache.accumulo.core.client.AccumuloException: Could not find
file /20//c-00000000 in [hdfs://localhost:9000/accumulo/tables]
>         at org.apache.accumulo.server.master.TabletGroupWatcher.mergeMetadataRecords(
>         at org.apache.accumulo.server.master.TabletGroupWatcher.updateMergeState(
>         at
> Caused by: Could not find file /20//c-00000000 in [hdfs://localhost:9000/accumulo/tables]
>         at org.apache.accumulo.server.fs.VolumeManagerImpl.getFullPath(
>         at org.apache.accumulo.server.util.MetadataTableUtil.createDeleteMutation(
>         at org.apache.accumulo.server.master.TabletGroupWatcher.mergeMetadataRecords(
>         ... 2 more
> {noformat}
> And the metadata table had c-00000000 listed here:
> {noformat}
> root@802 !METADATA> grep c-00000
> 20;00b581d7479230dd srv:dir []    /c-00000000
> 20< srv:dir []    /c-00000001
> {noformat}
> I was testing my table namespaces code but this seemed like an unrelated issue.

This message was sent by Atlassian JIRA

View raw message