[jira] [Updated] (HBASE-15232) Exceptions returned over multi RPC don't automatically trigger region location reloads
[
https://issues.apache.org/jira/browse/HBASE-15232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-15232:
--
Fix Version/s: 1.2.1
1.3.0
> Exceptions returned over multi RPC don't automatically trigger region
> location reloads
> --
>
> Key: HBASE-15232
> URL: https://issues.apache.org/jira/browse/HBASE-15232
> Project: HBase
> Issue Type: Sub-task
> Components: Client
>Reporter: Josh Elser
>Assignee: Josh Elser
> Fix For: 2.0.0, 1.3.0, 1.2.1
>
> Attachments: HBASE-15232-branch-1.002.patch, HBASE-15232.001.patch,
> HBASE-15232.002.patch, HBASE-15232.002.patch
>
>
> Follow-on for HBASE-15221:
> A work-around was added in HTableMultiplexer to work around an issue that
> AsyncProcess wasn't clearing the region location cache on Exception. This was
> stemming from the issue that the {{tableName}} is {{null}} because
> HTableMultiplexer is using the {{multi}} RPC. This causes an error that looks
> like:
> {noformat}
> [WARN] Coding error, see method javadoc. row=[B@1673eff, tableName=null
> {noformat}
> HBASE-15221 should fix HTableMultiplexer, but it would be good to push the
> fix down into AsyncProcess instead of using higher-level workarounds.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-15232) Exceptions returned over multi RPC don't automatically trigger region location reloads
[
https://issues.apache.org/jira/browse/HBASE-15232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Elser updated HBASE-15232:
---
Attachment: HBASE-15232-branch-1.002.patch
Here's a branch-1 patch, [~saint@gmail.com]
> Exceptions returned over multi RPC don't automatically trigger region
> location reloads
> --
>
> Key: HBASE-15232
> URL: https://issues.apache.org/jira/browse/HBASE-15232
> Project: HBase
> Issue Type: Sub-task
> Components: Client
>Reporter: Josh Elser
>Assignee: Josh Elser
> Fix For: 2.0.0
>
> Attachments: HBASE-15232-branch-1.002.patch, HBASE-15232.001.patch,
> HBASE-15232.002.patch, HBASE-15232.002.patch
>
>
> Follow-on for HBASE-15221:
> A work-around was added in HTableMultiplexer to work around an issue that
> AsyncProcess wasn't clearing the region location cache on Exception. This was
> stemming from the issue that the {{tableName}} is {{null}} because
> HTableMultiplexer is using the {{multi}} RPC. This causes an error that looks
> like:
> {noformat}
> [WARN] Coding error, see method javadoc. row=[B@1673eff, tableName=null
> {noformat}
> HBASE-15221 should fix HTableMultiplexer, but it would be good to push the
> fix down into AsyncProcess instead of using higher-level workarounds.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-15232) Exceptions returned over multi RPC don't automatically trigger region location reloads
[
https://issues.apache.org/jira/browse/HBASE-15232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-15232:
--
Resolution: Fixed
Fix Version/s: (was: 1.1.4)
(was: 1.2.1)
(was: 1.3.0)
Status: Resolved (was: Patch Available)
Applied to master branch. Doesn't go into branch-1. If you put up a version for
branch-1, I'll commit. Thanks for the patch [~elserj]
> Exceptions returned over multi RPC don't automatically trigger region
> location reloads
> --
>
> Key: HBASE-15232
> URL: https://issues.apache.org/jira/browse/HBASE-15232
> Project: HBase
> Issue Type: Sub-task
> Components: Client
>Reporter: Josh Elser
>Assignee: Josh Elser
> Fix For: 2.0.0
>
> Attachments: HBASE-15232.001.patch, HBASE-15232.002.patch,
> HBASE-15232.002.patch
>
>
> Follow-on for HBASE-15221:
> A work-around was added in HTableMultiplexer to work around an issue that
> AsyncProcess wasn't clearing the region location cache on Exception. This was
> stemming from the issue that the {{tableName}} is {{null}} because
> HTableMultiplexer is using the {{multi}} RPC. This causes an error that looks
> like:
> {noformat}
> [WARN] Coding error, see method javadoc. row=[B@1673eff, tableName=null
> {noformat}
> HBASE-15221 should fix HTableMultiplexer, but it would be good to push the
> fix down into AsyncProcess instead of using higher-level workarounds.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-15232) Exceptions returned over multi RPC don't automatically trigger region location reloads
[
https://issues.apache.org/jira/browse/HBASE-15232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-15232:
--
Attachment: HBASE-15232.002.patch
Retry
> Exceptions returned over multi RPC don't automatically trigger region
> location reloads
> --
>
> Key: HBASE-15232
> URL: https://issues.apache.org/jira/browse/HBASE-15232
> Project: HBase
> Issue Type: Sub-task
> Components: Client
>Reporter: Josh Elser
>Assignee: Josh Elser
> Fix For: 2.0.0, 1.3.0, 1.2.1, 1.1.4
>
> Attachments: HBASE-15232.001.patch, HBASE-15232.002.patch,
> HBASE-15232.002.patch
>
>
> Follow-on for HBASE-15221:
> A work-around was added in HTableMultiplexer to work around an issue that
> AsyncProcess wasn't clearing the region location cache on Exception. This was
> stemming from the issue that the {{tableName}} is {{null}} because
> HTableMultiplexer is using the {{multi}} RPC. This causes an error that looks
> like:
> {noformat}
> [WARN] Coding error, see method javadoc. row=[B@1673eff, tableName=null
> {noformat}
> HBASE-15221 should fix HTableMultiplexer, but it would be good to push the
> fix down into AsyncProcess instead of using higher-level workarounds.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-15232) Exceptions returned over multi RPC don't automatically trigger region location reloads
[
https://issues.apache.org/jira/browse/HBASE-15232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Elser updated HBASE-15232:
---
Attachment: HBASE-15232.002.patch
.002 Rebased on master, and tries to address Elliott's feedback.
> Exceptions returned over multi RPC don't automatically trigger region
> location reloads
> --
>
> Key: HBASE-15232
> URL: https://issues.apache.org/jira/browse/HBASE-15232
> Project: HBase
> Issue Type: Sub-task
> Components: Client
>Reporter: Josh Elser
>Assignee: Josh Elser
> Fix For: 2.0.0, 1.3.0, 1.2.1, 1.1.4
>
> Attachments: HBASE-15232.001.patch, HBASE-15232.002.patch
>
>
> Follow-on for HBASE-15221:
> A work-around was added in HTableMultiplexer to work around an issue that
> AsyncProcess wasn't clearing the region location cache on Exception. This was
> stemming from the issue that the {{tableName}} is {{null}} because
> HTableMultiplexer is using the {{multi}} RPC. This causes an error that looks
> like:
> {noformat}
> [WARN] Coding error, see method javadoc. row=[B@1673eff, tableName=null
> {noformat}
> HBASE-15221 should fix HTableMultiplexer, but it would be good to push the
> fix down into AsyncProcess instead of using higher-level workarounds.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-15232) Exceptions returned over multi RPC don't automatically trigger region location reloads
[
https://issues.apache.org/jira/browse/HBASE-15232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Elser updated HBASE-15232:
---
Attachment: (was: HBASE-15232.001.patch)
> Exceptions returned over multi RPC don't automatically trigger region
> location reloads
> --
>
> Key: HBASE-15232
> URL: https://issues.apache.org/jira/browse/HBASE-15232
> Project: HBase
> Issue Type: Sub-task
> Components: Client
>Reporter: Josh Elser
>Assignee: Josh Elser
> Fix For: 2.0.0, 1.3.0, 1.2.1, 1.1.4
>
> Attachments: HBASE-15232.001.patch
>
>
> Follow-on for HBASE-15221:
> A work-around was added in HTableMultiplexer to work around an issue that
> AsyncProcess wasn't clearing the region location cache on Exception. This was
> stemming from the issue that the {{tableName}} is {{null}} because
> HTableMultiplexer is using the {{multi}} RPC. This causes an error that looks
> like:
> {noformat}
> [WARN] Coding error, see method javadoc. row=[B@1673eff, tableName=null
> {noformat}
> HBASE-15221 should fix HTableMultiplexer, but it would be good to push the
> fix down into AsyncProcess instead of using higher-level workarounds.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-15232) Exceptions returned over multi RPC don't automatically trigger region location reloads
[
https://issues.apache.org/jira/browse/HBASE-15232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Elser updated HBASE-15232:
---
Attachment: HBASE-15232.001.patch
Reattaching for yetus. The tests that failed passed for me locally. Let's see
what a re-run does.
> Exceptions returned over multi RPC don't automatically trigger region
> location reloads
> --
>
> Key: HBASE-15232
> URL: https://issues.apache.org/jira/browse/HBASE-15232
> Project: HBase
> Issue Type: Sub-task
> Components: Client
>Reporter: Josh Elser
>Assignee: Josh Elser
> Fix For: 2.0.0, 1.3.0, 1.2.1, 1.1.4
>
> Attachments: HBASE-15232.001.patch
>
>
> Follow-on for HBASE-15221:
> A work-around was added in HTableMultiplexer to work around an issue that
> AsyncProcess wasn't clearing the region location cache on Exception. This was
> stemming from the issue that the {{tableName}} is {{null}} because
> HTableMultiplexer is using the {{multi}} RPC. This causes an error that looks
> like:
> {noformat}
> [WARN] Coding error, see method javadoc. row=[B@1673eff, tableName=null
> {noformat}
> HBASE-15221 should fix HTableMultiplexer, but it would be good to push the
> fix down into AsyncProcess instead of using higher-level workarounds.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-15232) Exceptions returned over multi RPC don't automatically trigger region location reloads
[
https://issues.apache.org/jira/browse/HBASE-15232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Elser updated HBASE-15232:
---
Status: Patch Available (was: Open)
> Exceptions returned over multi RPC don't automatically trigger region
> location reloads
> --
>
> Key: HBASE-15232
> URL: https://issues.apache.org/jira/browse/HBASE-15232
> Project: HBase
> Issue Type: Sub-task
> Components: Client
>Reporter: Josh Elser
>Assignee: Josh Elser
> Fix For: 2.0.0, 1.3.0, 1.2.1, 1.1.4
>
> Attachments: HBASE-15232.001.patch
>
>
> Follow-on for HBASE-15221:
> A work-around was added in HTableMultiplexer to work around an issue that
> AsyncProcess wasn't clearing the region location cache on Exception. This was
> stemming from the issue that the {{tableName}} is {{null}} because
> HTableMultiplexer is using the {{multi}} RPC. This causes an error that looks
> like:
> {noformat}
> [WARN] Coding error, see method javadoc. row=[B@1673eff, tableName=null
> {noformat}
> HBASE-15221 should fix HTableMultiplexer, but it would be good to push the
> fix down into AsyncProcess instead of using higher-level workarounds.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-15232) Exceptions returned over multi RPC don't automatically trigger region location reloads
[
https://issues.apache.org/jira/browse/HBASE-15232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Elser updated HBASE-15232:
---
Attachment: HBASE-15232.001.patch
.001 Here's what I was thinking. I was able to piggy-back off of the test added
with HBASE-12198 which makes me confident we're doing the right thing.
Letting yetus chew on this while I run it through the test suite locally too.
> Exceptions returned over multi RPC don't automatically trigger region
> location reloads
> --
>
> Key: HBASE-15232
> URL: https://issues.apache.org/jira/browse/HBASE-15232
> Project: HBase
> Issue Type: Sub-task
> Components: Client
>Reporter: Josh Elser
>Assignee: Josh Elser
> Fix For: 2.0.0, 1.3.0, 1.2.1, 1.1.4
>
> Attachments: HBASE-15232.001.patch
>
>
> Follow-on for HBASE-15221:
> A work-around was added in HTableMultiplexer to work around an issue that
> AsyncProcess wasn't clearing the region location cache on Exception. This was
> stemming from the issue that the {{tableName}} is {{null}} because
> HTableMultiplexer is using the {{multi}} RPC. This causes an error that looks
> like:
> {noformat}
> [WARN] Coding error, see method javadoc. row=[B@1673eff, tableName=null
> {noformat}
> HBASE-15221 should fix HTableMultiplexer, but it would be good to push the
> fix down into AsyncProcess instead of using higher-level workarounds.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-15232) Exceptions returned over multi RPC don't automatically trigger region location reloads
[
https://issues.apache.org/jira/browse/HBASE-15232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Elser updated HBASE-15232:
---
Summary: Exceptions returned over multi RPC don't automatically trigger
region location reloads (was: Exceptions returned over multi RPC don't trigger
region location reloads)
> Exceptions returned over multi RPC don't automatically trigger region
> location reloads
> --
>
> Key: HBASE-15232
> URL: https://issues.apache.org/jira/browse/HBASE-15232
> Project: HBase
> Issue Type: Sub-task
> Components: Client
>Reporter: Josh Elser
>Assignee: Josh Elser
> Fix For: 2.0.0, 1.3.0, 1.2.1, 1.1.4
>
>
> Follow-on for HBASE-15221:
> A work-around was added in HTableMultiplexer to work around an issue that
> AsyncProcess wasn't clearing the region location cache on Exception. This was
> stemming from the issue that the {{tableName}} is {{null}} because
> HTableMultiplexer is using the {{multi}} RPC. This causes an error that looks
> like:
> {noformat}
> [WARN] Coding error, see method javadoc. row=[B@1673eff, tableName=null
> {noformat}
> HBASE-15221 should fix HTableMultiplexer, but it would be good to push the
> fix down into AsyncProcess instead of using higher-level workarounds.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
