[
https://issues.apache.org/jira/browse/HAMA-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12706698#action_12706698
]
Edward J. Yoon commented on HAMA-182:
-------------------------------------
When too many families (100) are in one table, I received below messages.
org.apache.hadoop.hbase.client.RetriesExhaustedException: Trying to contact
region server 61.247.200.35:60020 for region
DenseMatrix_randonmwq,,1241660972061, row '000000000000442', but failed after
10 attempts.
Exceptions:
java.io.IOException: Call to /61.247.200.35:60020 failed on local exception:
java.io.EOFException
java.net.ConnectException: Call to /61.247.200.35:60020 failed on connection
exception: java.net.ConnectException: Connection refused
java.net.ConnectException: Call to /61.247.200.35:60020 failed on connection
exception: java.net.ConnectException: Connection refused
java.net.ConnectException: Call to /61.247.200.35:60020 failed on connection
exception: java.net.ConnectException: Connection refused
java.net.ConnectException: Call to /61.247.200.35:60020 failed on connection
exception: java.net.ConnectException: Connection refused
java.net.ConnectException: Call to /61.247.200.35:60020 failed on connection
exception: java.net.ConnectException: Connection refused
java.net.ConnectException: Call to /61.247.200.35:60020 failed on connection
exception: java.net.ConnectException: Connection refused
java.net.ConnectException: Call to /61.247.200.35:60020 failed on connection
exception: java.net.ConnectException: Connection refused
java.net.ConnectException: Call to /61.247.200.35:60020 failed on connection
exception: java.net.ConnectException: Connection refused
java.net.ConnectException: Call to /61.247.200.35:60020 failed on connection
exception: java.net.ConnectException: Connection refused
at
org.apache.hadoop.hbase.client.HConnectionManager$TableServers.getRegionServerWithRetries(HConnectionManager.java:841)
at
org.apache.hadoop.hbase.client.HConnectionManager$TableServers.processBatchOfRows(HConnectionManager.java:932)
at org.apache.hadoop.hbase.client.HTable.flushCommits(HTable.java:1372)
at org.apache.hadoop.hbase.client.HTable.commit(HTable.java:1316)
at org.apache.hadoop.hbase.client.HTable.commit(HTable.java:1296)
at
org.apache.hama.mapred.VectorOutputFormat$TableRecordWriter.write(VectorOutputFormat.java:71)
at
org.apache.hama.mapred.VectorOutputFormat$TableRecordWriter.write(VectorOutputFormat.java:51)
at org.apache.hadoop.mapred.ReduceTask$3.collect(ReduceTask.java:410)
at
org.apache.hama.mapred.RandomMatrixReduce.reduce(RandomMatrixReduce.java:71)
at
org.apache.hama.mapred.RandomMatrixReduce.reduce(RandomMatrixReduce.java:36)
at org.apache.hadoop.mapred.ReduceTask.run(ReduceTask.java:436)
at org.apache.hadoop.mapred.Child.main(Child.java:158)
> Seperate column families
> ------------------------
>
> Key: HAMA-182
> URL: https://issues.apache.org/jira/browse/HAMA-182
> Project: Hama
> Issue Type: Improvement
> Components: implementation
> Affects Versions: 0.1.0
> Reporter: Edward J. Yoon
> Assignee: Edward J. Yoon
> Fix For: 0.1.0
>
> Attachments: columns.patch
>
>
> The all columns are stored in a single column family. I propose to separate
> column families by column index range so that we reduces I/O during
> column-based process.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.