[jira] [Updated] (HBASE-15390) Unnecessary MetaCache evictions cause elevated number of requests to meta
[ https://issues.apache.org/jira/browse/HBASE-15390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Antonov updated HBASE-15390: Issue Type: Sub-task (was: Bug) Parent: HBASE-15654 > Unnecessary MetaCache evictions cause elevated number of requests to meta > - > > Key: HBASE-15390 > URL: https://issues.apache.org/jira/browse/HBASE-15390 > Project: HBase > Issue Type: Sub-task > Components: Client >Affects Versions: 1.2.0 >Reporter: Mikhail Antonov >Assignee: Mikhail Antonov >Priority: Blocker > Fix For: 2.0.0, 1.3.0 > > Attachments: HBASE-15390-addendum.patch, > HBASE-15390.branch-1.3.v1.patch, HBASE-15390.v1.patch > > > - In ClientExceptionsUtil#findException() we don't unwrap correctly all > remote exceptions but a few selected ones; >more specifically, we don't unwrap correctly all remote exceptions where > getCause() exception doesn't have a constructor (String message) > - In AsyncProcess#receiveGlobalFailure() we don't check for > #isMetaClearingException() if tableName is null > - We don't have metric on client side to track number of cache drops -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-15390) Unnecessary MetaCache evictions cause elevated number of requests to meta
[ https://issues.apache.org/jira/browse/HBASE-15390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Antonov updated HBASE-15390: Status: Open (was: Patch Available) > Unnecessary MetaCache evictions cause elevated number of requests to meta > - > > Key: HBASE-15390 > URL: https://issues.apache.org/jira/browse/HBASE-15390 > Project: HBase > Issue Type: Bug > Components: Client >Affects Versions: 1.2.0 >Reporter: Mikhail Antonov >Assignee: Mikhail Antonov >Priority: Blocker > Fix For: 1.3.0, 1.2.1 > > Attachments: HBASE-15390.branch-1.3.v1.patch, HBASE-15390.v1.patch > > > - In ClientExceptionsUtil#findException() we don't unwrap correctly all > remote exceptions but a few selected ones; >more specifically, we don't unwrap correctly all remote exceptions where > getCause() exception doesn't have a constructor (String message) > - In AsyncProcess#receiveGlobalFailure() we don't check for > #isMetaClearingException() if tableName is null > - We don't have metric on client side to track number of cache drops -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-15390) Unnecessary MetaCache evictions cause elevated number of requests to meta
[ https://issues.apache.org/jira/browse/HBASE-15390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Antonov updated HBASE-15390: Attachment: HBASE-15390-addendum.patch Attached fixes to ClientExceptionsUtil which fixes infinite loop in findException() (catch by [~eclark]) > Unnecessary MetaCache evictions cause elevated number of requests to meta > - > > Key: HBASE-15390 > URL: https://issues.apache.org/jira/browse/HBASE-15390 > Project: HBase > Issue Type: Bug > Components: Client >Affects Versions: 1.2.0 >Reporter: Mikhail Antonov >Assignee: Mikhail Antonov >Priority: Blocker > Fix For: 2.0.0, 1.3.0 > > Attachments: HBASE-15390-addendum.patch, > HBASE-15390.branch-1.3.v1.patch, HBASE-15390.v1.patch > > > - In ClientExceptionsUtil#findException() we don't unwrap correctly all > remote exceptions but a few selected ones; >more specifically, we don't unwrap correctly all remote exceptions where > getCause() exception doesn't have a constructor (String message) > - In AsyncProcess#receiveGlobalFailure() we don't check for > #isMetaClearingException() if tableName is null > - We don't have metric on client side to track number of cache drops -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-15390) Unnecessary MetaCache evictions cause elevated number of requests to meta
[ https://issues.apache.org/jira/browse/HBASE-15390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Antonov updated HBASE-15390: Attachment: HBASE-15390.v1.patch patch for master > Unnecessary MetaCache evictions cause elevated number of requests to meta > - > > Key: HBASE-15390 > URL: https://issues.apache.org/jira/browse/HBASE-15390 > Project: HBase > Issue Type: Bug > Components: Client >Affects Versions: 1.2.0 >Reporter: Mikhail Antonov >Assignee: Mikhail Antonov >Priority: Blocker > Fix For: 1.3.0, 1.2.1 > > Attachments: HBASE-15390.branch-1.3.v1.patch, HBASE-15390.v1.patch > > > - In ClientExceptionsUtil#findException() we don't unwrap correctly all > remote exceptions but a few selected ones; >more specifically, we don't unwrap correctly all remote exceptions where > getCause() exception doesn't have a constructor (String message) > - In AsyncProcess#receiveGlobalFailure() we don't check for > #isMetaClearingException() if tableName is null > - We don't have metric on client side to track number of cache drops -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-15390) Unnecessary MetaCache evictions cause elevated number of requests to meta
[ https://issues.apache.org/jira/browse/HBASE-15390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Antonov updated HBASE-15390: Resolution: Fixed Status: Resolved (was: Patch Available) > Unnecessary MetaCache evictions cause elevated number of requests to meta > - > > Key: HBASE-15390 > URL: https://issues.apache.org/jira/browse/HBASE-15390 > Project: HBase > Issue Type: Bug > Components: Client >Affects Versions: 1.2.0 >Reporter: Mikhail Antonov >Assignee: Mikhail Antonov >Priority: Blocker > Fix For: 1.3.0, 1.2.1 > > Attachments: HBASE-15390.branch-1.3.v1.patch, HBASE-15390.v1.patch > > > - In ClientExceptionsUtil#findException() we don't unwrap correctly all > remote exceptions but a few selected ones; >more specifically, we don't unwrap correctly all remote exceptions where > getCause() exception doesn't have a constructor (String message) > - In AsyncProcess#receiveGlobalFailure() we don't check for > #isMetaClearingException() if tableName is null > - We don't have metric on client side to track number of cache drops -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-15390) Unnecessary MetaCache evictions cause elevated number of requests to meta
[ https://issues.apache.org/jira/browse/HBASE-15390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Antonov updated HBASE-15390: Status: Patch Available (was: Open) > Unnecessary MetaCache evictions cause elevated number of requests to meta > - > > Key: HBASE-15390 > URL: https://issues.apache.org/jira/browse/HBASE-15390 > Project: HBase > Issue Type: Bug > Components: Client >Affects Versions: 1.2.0 >Reporter: Mikhail Antonov >Assignee: Mikhail Antonov >Priority: Blocker > Fix For: 1.3.0, 1.2.1 > > Attachments: HBASE-15390.branch-1.3.v1.patch, HBASE-15390.v1.patch > > > - In ClientExceptionsUtil#findException() we don't unwrap correctly all > remote exceptions but a few selected ones; >more specifically, we don't unwrap correctly all remote exceptions where > getCause() exception doesn't have a constructor (String message) > - In AsyncProcess#receiveGlobalFailure() we don't check for > #isMetaClearingException() if tableName is null > - We don't have metric on client side to track number of cache drops -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-15390) Unnecessary MetaCache evictions cause elevated number of requests to meta
[ https://issues.apache.org/jira/browse/HBASE-15390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Antonov updated HBASE-15390: Fix Version/s: (was: 1.2.1) 2.0.0 > Unnecessary MetaCache evictions cause elevated number of requests to meta > - > > Key: HBASE-15390 > URL: https://issues.apache.org/jira/browse/HBASE-15390 > Project: HBase > Issue Type: Bug > Components: Client >Affects Versions: 1.2.0 >Reporter: Mikhail Antonov >Assignee: Mikhail Antonov >Priority: Blocker > Fix For: 2.0.0, 1.3.0 > > Attachments: HBASE-15390.branch-1.3.v1.patch, HBASE-15390.v1.patch > > > - In ClientExceptionsUtil#findException() we don't unwrap correctly all > remote exceptions but a few selected ones; >more specifically, we don't unwrap correctly all remote exceptions where > getCause() exception doesn't have a constructor (String message) > - In AsyncProcess#receiveGlobalFailure() we don't check for > #isMetaClearingException() if tableName is null > - We don't have metric on client side to track number of cache drops -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-15390) Unnecessary MetaCache evictions cause elevated number of requests to meta
[ https://issues.apache.org/jira/browse/HBASE-15390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Antonov updated HBASE-15390: Status: Patch Available (was: Open) > Unnecessary MetaCache evictions cause elevated number of requests to meta > - > > Key: HBASE-15390 > URL: https://issues.apache.org/jira/browse/HBASE-15390 > Project: HBase > Issue Type: Bug > Components: Client >Affects Versions: 1.2.0 >Reporter: Mikhail Antonov >Assignee: Mikhail Antonov >Priority: Blocker > Fix For: 1.3.0, 1.2.1 > > Attachments: HBASE-15390.branch-1.3.v1.patch > > > - In ClientExceptionsUtil#findException() we don't unwrap correctly all > remote exceptions but a few selected ones; >more specifically, we don't unwrap correctly all remote exceptions where > getCause() exception doesn't have a constructor (String message) > - In AsyncProcess#receiveGlobalFailure() we don't check for > #isMetaClearingException() if tableName is null > - We don't have metric on client side to track number of cache drops -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-15390) Unnecessary MetaCache evictions cause elevated number of requests to meta
[ https://issues.apache.org/jira/browse/HBASE-15390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Antonov updated HBASE-15390: Attachment: HBASE-15390.branch-1.3.v1.patch > Unnecessary MetaCache evictions cause elevated number of requests to meta > - > > Key: HBASE-15390 > URL: https://issues.apache.org/jira/browse/HBASE-15390 > Project: HBase > Issue Type: Bug > Components: Client >Affects Versions: 1.2.0 >Reporter: Mikhail Antonov >Assignee: Mikhail Antonov >Priority: Blocker > Fix For: 1.3.0, 1.2.1 > > Attachments: HBASE-15390.branch-1.3.v1.patch > > > - In ClientExceptionsUtil#findException() we don't unwrap correctly all > remote exceptions but a few selected ones; >more specifically, we don't unwrap correctly all remote exceptions where > getCause() exception doesn't have a constructor (String message) > - In AsyncProcess#receiveGlobalFailure() we don't check for > #isMetaClearingException() if tableName is null > - We don't have metric on client side to track number of cache drops -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-15390) Unnecessary MetaCache evictions cause elevated number of requests to meta
[ https://issues.apache.org/jira/browse/HBASE-15390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Antonov updated HBASE-15390: Description: - In ClientExceptionsUtil#findException() we don't unwrap correctly all remote exceptions but a few selected ones; more specifically, we don't unwrap correctly all remote exceptions where getCause() exception doesn't have a constructor (String message) - In AsyncProcess#receiveGlobalFailure() we don't check for #isMetaClearingException() if tableName is null - We don't have metric on client side to track number of cache drops was: - In ClientExceptionsUtil#findException() we don't unwrap correctly all remote exceptions but a few selected ones - In AsyncProcess#receiveGlobalFailure() we don't check for #isMetaClearingException() if tableName is null - We don't have metric on client side to track number of cache drops > Unnecessary MetaCache evictions cause elevated number of requests to meta > - > > Key: HBASE-15390 > URL: https://issues.apache.org/jira/browse/HBASE-15390 > Project: HBase > Issue Type: Bug > Components: Client >Affects Versions: 1.2.0 >Reporter: Mikhail Antonov >Assignee: Mikhail Antonov >Priority: Blocker > Fix For: 1.3.0, 1.2.1 > > > - In ClientExceptionsUtil#findException() we don't unwrap correctly all > remote exceptions but a few selected ones; >more specifically, we don't unwrap correctly all remote exceptions where > getCause() exception doesn't have a constructor (String message) > - In AsyncProcess#receiveGlobalFailure() we don't check for > #isMetaClearingException() if tableName is null > - We don't have metric on client side to track number of cache drops -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-15390) Unnecessary MetaCache evictions cause elevated number of requests to meta
[ https://issues.apache.org/jira/browse/HBASE-15390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Antonov updated HBASE-15390: Description: - In ClientExceptionsUtil#findException() we don't unwrap correctly all remote exceptions but a few selected ones - In AsyncProcess#receiveGlobalFailure() we don't check for #isMs was: In #isMetaClearingException() we're checking for CallQueueTooBigException, but under debugger in tests I saw that what we're really getting in here is RemoteWithExtrasException, which doesn't allow to easily unwrap CQTBE from it, since it's stored in the classname field, and findException() or unwrapRemoteException() fail to unwrap it correctly. I think we'd have the same behavior with other exceptions wrapper this way. > Unnecessary MetaCache evictions cause elevated number of requests to meta > - > > Key: HBASE-15390 > URL: https://issues.apache.org/jira/browse/HBASE-15390 > Project: HBase > Issue Type: Bug > Components: Client >Affects Versions: 1.2.0 >Reporter: Mikhail Antonov >Assignee: Mikhail Antonov >Priority: Blocker > Fix For: 1.3.0, 1.2.1 > > > - In ClientExceptionsUtil#findException() we don't unwrap correctly all > remote exceptions but a few selected ones > - In AsyncProcess#receiveGlobalFailure() we don't check for #isMs -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-15390) Unnecessary MetaCache evictions cause elevated number of requests to meta
[ https://issues.apache.org/jira/browse/HBASE-15390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Antonov updated HBASE-15390: Description: - In ClientExceptionsUtil#findException() we don't unwrap correctly all remote exceptions but a few selected ones - In AsyncProcess#receiveGlobalFailure() we don't check for #isMetaClearingException() if tableName is null - We don't have metric on client side to track number of cache drops was: - In ClientExceptionsUtil#findException() we don't unwrap correctly all remote exceptions but a few selected ones - In AsyncProcess#receiveGlobalFailure() we don't check for #isMs > Unnecessary MetaCache evictions cause elevated number of requests to meta > - > > Key: HBASE-15390 > URL: https://issues.apache.org/jira/browse/HBASE-15390 > Project: HBase > Issue Type: Bug > Components: Client >Affects Versions: 1.2.0 >Reporter: Mikhail Antonov >Assignee: Mikhail Antonov >Priority: Blocker > Fix For: 1.3.0, 1.2.1 > > > - In ClientExceptionsUtil#findException() we don't unwrap correctly all > remote exceptions but a few selected ones > - In AsyncProcess#receiveGlobalFailure() we don't check for > #isMetaClearingException() if tableName is null > - We don't have metric on client side to track number of cache drops -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-15390) Unnecessary MetaCache evictions cause elevated number of requests to meta
[ https://issues.apache.org/jira/browse/HBASE-15390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Antonov updated HBASE-15390: Summary: Unnecessary MetaCache evictions cause elevated number of requests to meta (was: ClientExceptionUtils doesn't handle CallQueueTooBigException properly) > Unnecessary MetaCache evictions cause elevated number of requests to meta > - > > Key: HBASE-15390 > URL: https://issues.apache.org/jira/browse/HBASE-15390 > Project: HBase > Issue Type: Bug > Components: Client >Affects Versions: 1.2.0 >Reporter: Mikhail Antonov >Assignee: Mikhail Antonov >Priority: Blocker > Fix For: 1.3.0, 1.2.1 > > > In #isMetaClearingException() we're checking for CallQueueTooBigException, > but under debugger in tests I saw that what we're really getting in here is > RemoteWithExtrasException, which doesn't allow to easily unwrap CQTBE from > it, since it's stored in the classname field, and findException() or > unwrapRemoteException() fail to unwrap it correctly. > I think we'd have the same behavior with other exceptions wrapper this way. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
