[jira] [Updated] (HBASE-3850) Log more details when a scanner lease expires
[
https://issues.apache.org/jira/browse/HBASE-3850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhihong Yu updated HBASE-3850:
--
Attachment: 3850-v3.txt
Fixed spacing around else.
Log more details when a scanner lease expires
-
Key: HBASE-3850
URL: https://issues.apache.org/jira/browse/HBASE-3850
Project: HBase
Issue Type: Improvement
Components: regionserver
Reporter: Benoit Sigoure
Assignee: Darren Haas
Priority: Critical
Fix For: 0.94.0
Attachments: 3850-v3.txt, HBASE-3850.trunk.v1.patch,
HBASE-3850.trunk.v2.patch
The message logged by the RegionServer when a Scanner lease expires isn't as
useful as it could be. {{Scanner 4765412385779771089 lease expired}} - most
clients don't log their scanner ID, so it's really hard to figure out what
was going on. I think it would be useful to at least log the name of the
region on which the Scanner was open, and it would be great to have the
ip:port of the client that had that lease too.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-3850) Log more details when a scanner lease expires
[
https://issues.apache.org/jira/browse/HBASE-3850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Darren Haas updated HBASE-3850:
---
Attachment: HBASE-3850.trunk.v1.patch
The attached file is a patch
Log more details when a scanner lease expires
-
Key: HBASE-3850
URL: https://issues.apache.org/jira/browse/HBASE-3850
Project: HBase
Issue Type: Improvement
Components: regionserver
Reporter: Benoit Sigoure
Assignee: Mubarak Seyed
Priority: Critical
Attachments: HBASE-3850.trunk.v1.patch
The message logged by the RegionServer when a Scanner lease expires isn't as
useful as it could be. {{Scanner 4765412385779771089 lease expired}} - most
clients don't log their scanner ID, so it's really hard to figure out what
was going on. I think it would be useful to at least log the name of the
region on which the Scanner was open, and it would be great to have the
ip:port of the client that had that lease too.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-3850) Log more details when a scanner lease expires
[
https://issues.apache.org/jira/browse/HBASE-3850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhihong Yu updated HBASE-3850:
--
Fix Version/s: 0.94.0
Hadoop Flags: Reviewed
Log more details when a scanner lease expires
-
Key: HBASE-3850
URL: https://issues.apache.org/jira/browse/HBASE-3850
Project: HBase
Issue Type: Improvement
Components: regionserver
Reporter: Benoit Sigoure
Assignee: Darren Haas
Priority: Critical
Fix For: 0.94.0
Attachments: HBASE-3850.trunk.v1.patch
The message logged by the RegionServer when a Scanner lease expires isn't as
useful as it could be. {{Scanner 4765412385779771089 lease expired}} - most
clients don't log their scanner ID, so it's really hard to figure out what
was going on. I think it would be useful to at least log the name of the
region on which the Scanner was open, and it would be great to have the
ip:port of the client that had that lease too.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-3850) Log more details when a scanner lease expires
[
https://issues.apache.org/jira/browse/HBASE-3850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Darren Haas updated HBASE-3850:
---
Attachment: HBASE-3850.trunk.v2.patch
Attached file contains updated patch
Log more details when a scanner lease expires
-
Key: HBASE-3850
URL: https://issues.apache.org/jira/browse/HBASE-3850
Project: HBase
Issue Type: Improvement
Components: regionserver
Reporter: Benoit Sigoure
Assignee: Darren Haas
Priority: Critical
Fix For: 0.94.0
Attachments: HBASE-3850.trunk.v1.patch, HBASE-3850.trunk.v2.patch
The message logged by the RegionServer when a Scanner lease expires isn't as
useful as it could be. {{Scanner 4765412385779771089 lease expired}} - most
clients don't log their scanner ID, so it's really hard to figure out what
was going on. I think it would be useful to at least log the name of the
region on which the Scanner was open, and it would be great to have the
ip:port of the client that had that lease too.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-3850) Log more details when a scanner lease expires
[
https://issues.apache.org/jira/browse/HBASE-3850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-3850:
-
Priority: Critical (was: Minor)
Tags: noob
Log more details when a scanner lease expires
-
Key: HBASE-3850
URL: https://issues.apache.org/jira/browse/HBASE-3850
Project: HBase
Issue Type: Improvement
Components: regionserver
Reporter: Benoit Sigoure
Priority: Critical
The message logged by the RegionServer when a Scanner lease expires isn't as
useful as it could be. {{Scanner 4765412385779771089 lease expired}} - most
clients don't log their scanner ID, so it's really hard to figure out what
was going on. I think it would be useful to at least log the name of the
region on which the Scanner was open, and it would be great to have the
ip:port of the client that had that lease too.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
