[jira] Updated: (HBASE-2931) Do not throw RuntimeExceptions in RPC/HbaseObjectWritable code, ensure we log and rethrow as IOE
[ https://issues.apache.org/jira/browse/HBASE-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Ranganathan updated HBASE-2931: --- Attachment: HBASE-2931.patch Simple patch - posting directly instead of review board. Moves the newly added class down to the end of the object writeable opcode list so that all subsequent op-codes do not change. Also added some logging. Do not throw RuntimeExceptions in RPC/HbaseObjectWritable code, ensure we log and rethrow as IOE Key: HBASE-2931 URL: https://issues.apache.org/jira/browse/HBASE-2931 Project: HBase Issue Type: Bug Reporter: Jonathan Gray Priority: Critical Fix For: 0.90.0 Attachments: HBASE-2931.patch When there are issues with RPC and HbaseObjectWritable, primarily when server and client have different jars, the only thing that happens is the client will receive an EOF exception. The server does not log what happened at all and the client does not receive a server trace, rather the server seems to close the connection and the client gets an EOF because it tries to read off of a closed stream. We need to ensure that we catch, log, and rethrow as IOE any exceptions that may occur because of an issue with RPC or HbaseObjectWritable. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (HBASE-2931) Do not throw RuntimeExceptions in RPC/HbaseObjectWritable code, ensure we log and rethrow as IOE
[ https://issues.apache.org/jira/browse/HBASE-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Ranganathan reassigned HBASE-2931: -- Assignee: Karthik Ranganathan Do not throw RuntimeExceptions in RPC/HbaseObjectWritable code, ensure we log and rethrow as IOE Key: HBASE-2931 URL: https://issues.apache.org/jira/browse/HBASE-2931 Project: HBase Issue Type: Bug Reporter: Jonathan Gray Assignee: Karthik Ranganathan Priority: Critical Fix For: 0.90.0 Attachments: HBASE-2931.patch When there are issues with RPC and HbaseObjectWritable, primarily when server and client have different jars, the only thing that happens is the client will receive an EOF exception. The server does not log what happened at all and the client does not receive a server trace, rather the server seems to close the connection and the client gets an EOF because it tries to read off of a closed stream. We need to ensure that we catch, log, and rethrow as IOE any exceptions that may occur because of an issue with RPC or HbaseObjectWritable. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HBASE-50) Snapshot of table
[ https://issues.apache.org/jira/browse/HBASE-50?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12901206#action_12901206 ] HBase Review Board commented on HBASE-50: - Message from: Ted Yu ted...@yahoo.com --- This is an automatically generated e-mail. To reply, visit: http://review.cloudera.org/r/467/#review995 --- bin/add_snapshot_family.rb http://review.cloudera.org/r/467/#comment3204 Please remove this comment. src/main/java/org/apache/hadoop/hbase/HConstants.java http://review.cloudera.org/r/467/#comment3203 Should the archive directory be named .archive ? - Ted Snapshot of table - Key: HBASE-50 URL: https://issues.apache.org/jira/browse/HBASE-50 Project: HBase Issue Type: New Feature Reporter: Billy Pearson Assignee: Li Chongxin Priority: Minor Attachments: HBase Snapshot Design Report V2.pdf, HBase Snapshot Design Report V3.pdf, HBase Snapshot Implementation Plan.pdf, Snapshot Class Diagram.png Havening an option to take a snapshot of a table would be vary useful in production. What I would like to see this option do is do a merge of all the data into one or more files stored in the same folder on the dfs. This way we could save data in case of a software bug in hadoop or user code. The other advantage would be to be able to export a table to multi locations. Say I had a read_only table that must be online. I could take a snapshot of it when needed and export it to a separate data center and have it loaded there and then i would have it online at multi data centers for load balancing and failover. I understand that hadoop takes the need out of havening backup to protect from failed servers, but this does not protect use from software bugs that might delete or alter data in ways we did not plan. We should have a way we can roll back a dataset. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (HBASE-2931) Do not throw RuntimeExceptions in RPC/HbaseObjectWritable code, ensure we log and rethrow as IOE
[ https://issues.apache.org/jira/browse/HBASE-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HBASE-2931. -- Hadoop Flags: [Reviewed] Resolution: Fixed Applied to TRUNK. Thanks for the patch Karthik. Do not throw RuntimeExceptions in RPC/HbaseObjectWritable code, ensure we log and rethrow as IOE Key: HBASE-2931 URL: https://issues.apache.org/jira/browse/HBASE-2931 Project: HBase Issue Type: Bug Reporter: Jonathan Gray Assignee: Karthik Ranganathan Priority: Critical Fix For: 0.90.0 Attachments: HBASE-2931.patch When there are issues with RPC and HbaseObjectWritable, primarily when server and client have different jars, the only thing that happens is the client will receive an EOF exception. The server does not log what happened at all and the client does not receive a server trace, rather the server seems to close the connection and the client gets an EOF because it tries to read off of a closed stream. We need to ensure that we catch, log, and rethrow as IOE any exceptions that may occur because of an issue with RPC or HbaseObjectWritable. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
