[jira] Updated: (ZOOKEEPER-518) DEBUG message for outstanding proposals in leader should be moved to trace.

2009-09-03 Thread Prasad Gawande (JIRA) 

 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prasad Gawande updated ZOOKEEPER-518:
-

  Component/s: (was: server)
   tests
   Issue Type: Test  (was: Bug)
  Environment: Non specific
Affects Version/s: (was: 3.1.1)
   (was: 3.2.0)
   4.0.0
 Release Note: The released of this module should be done only in 
apache org as this module is move to the debug to trace since it will cause 
really high latenciesinin response times from zookeeper services in case folks 
want to use DEBUGlogging for servers.

 DEBUG message for outstanding proposals in leader should be moved to trace.
 ---

 Key: ZOOKEEPER-518
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-518
 Project: Zookeeper
  Issue Type: Test
  Components: tests
Affects Versions: 4.0.0
 Environment: Non specific
Reporter: Mahadev konar
Assignee: Patrick Hunt
 Fix For: 3.2.1, 3.3.0

 Attachments: ZOOKEEPER-518.patch


 this is the code in Leader.java 
 {code}
  if (LOG.isDebugEnabled()) {
 LOG.debug(Ack zxid: 0x + Long.toHexString(zxid));
 for (Proposal p : outstandingProposals.values()) {
 long packetZxid = p.packet.getZxid();
 LOG.debug(outstanding proposal: 0x
 + Long.toHexString(packetZxid));
 }
 LOG.debug(outstanding proposals all);
 }
 {code}
 We should move this debug to trace since it will cause really high latencies 
 in response times from zookeeper servers in case folks want to use DEBUG 
 logging for servers.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (ZOOKEEPER-518) DEBUG message for outstanding proposals in leader should be moved to trace.

2009-08-26 Thread Patrick Hunt (JIRA) 

 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Patrick Hunt updated ZOOKEEPER-518:
---

  Component/s: server
Affects Version/s: 3.1.1
   3.2.0

 DEBUG message for outstanding proposals in leader should be moved to trace.
 ---

 Key: ZOOKEEPER-518
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-518
 Project: Zookeeper
  Issue Type: Bug
  Components: server
Affects Versions: 3.1.1, 3.2.0
Reporter: Mahadev konar
Assignee: Patrick Hunt
 Fix For: 3.2.1, 3.3.0


 this is the code in Leader.java 
 {code}
  if (LOG.isDebugEnabled()) {
 LOG.debug(Ack zxid: 0x + Long.toHexString(zxid));
 for (Proposal p : outstandingProposals.values()) {
 long packetZxid = p.packet.getZxid();
 LOG.debug(outstanding proposal: 0x
 + Long.toHexString(packetZxid));
 }
 LOG.debug(outstanding proposals all);
 }
 {code}
 We should move this debug to trace since it will cause really high latencies 
 in response times from zookeeper servers in case folks want to use DEBUG 
 logging for servers.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (ZOOKEEPER-518) DEBUG message for outstanding proposals in leader should be moved to trace.

2009-08-26 Thread Patrick Hunt (JIRA) 

 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Patrick Hunt updated ZOOKEEPER-518:
---

Fix Version/s: 3.2.1
 Assignee: Patrick Hunt  (was: Mahadev konar)

 DEBUG message for outstanding proposals in leader should be moved to trace.
 ---

 Key: ZOOKEEPER-518
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-518
 Project: Zookeeper
  Issue Type: Bug
  Components: server
Affects Versions: 3.1.1, 3.2.0
Reporter: Mahadev konar
Assignee: Patrick Hunt
 Fix For: 3.2.1, 3.3.0


 this is the code in Leader.java 
 {code}
  if (LOG.isDebugEnabled()) {
 LOG.debug(Ack zxid: 0x + Long.toHexString(zxid));
 for (Proposal p : outstandingProposals.values()) {
 long packetZxid = p.packet.getZxid();
 LOG.debug(outstanding proposal: 0x
 + Long.toHexString(packetZxid));
 }
 LOG.debug(outstanding proposals all);
 }
 {code}
 We should move this debug to trace since it will cause really high latencies 
 in response times from zookeeper servers in case folks want to use DEBUG 
 logging for servers.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (ZOOKEEPER-518) DEBUG message for outstanding proposals in leader should be moved to trace.

2009-08-26 Thread Patrick Hunt (JIRA) 

 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Patrick Hunt updated ZOOKEEPER-518:
---

Status: Patch Available  (was: Open)

 DEBUG message for outstanding proposals in leader should be moved to trace.
 ---

 Key: ZOOKEEPER-518
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-518
 Project: Zookeeper
  Issue Type: Bug
  Components: server
Affects Versions: 3.2.0, 3.1.1
Reporter: Mahadev konar
Assignee: Patrick Hunt
 Fix For: 3.2.1, 3.3.0

 Attachments: ZOOKEEPER-518.patch


 this is the code in Leader.java 
 {code}
  if (LOG.isDebugEnabled()) {
 LOG.debug(Ack zxid: 0x + Long.toHexString(zxid));
 for (Proposal p : outstandingProposals.values()) {
 long packetZxid = p.packet.getZxid();
 LOG.debug(outstanding proposal: 0x
 + Long.toHexString(packetZxid));
 }
 LOG.debug(outstanding proposals all);
 }
 {code}
 We should move this debug to trace since it will cause really high latencies 
 in response times from zookeeper servers in case folks want to use DEBUG 
 logging for servers.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (ZOOKEEPER-518) DEBUG message for outstanding proposals in leader should be moved to trace.

2009-08-26 Thread Patrick Hunt (JIRA) 

 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Patrick Hunt updated ZOOKEEPER-518:
---

Attachment: ZOOKEEPER-518.patch

this patch changes from debug to trace, that is all. I expect the qabot to fail 
(no test changed)

 DEBUG message for outstanding proposals in leader should be moved to trace.
 ---

 Key: ZOOKEEPER-518
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-518
 Project: Zookeeper
  Issue Type: Bug
  Components: server
Affects Versions: 3.1.1, 3.2.0
Reporter: Mahadev konar
Assignee: Patrick Hunt
 Fix For: 3.2.1, 3.3.0

 Attachments: ZOOKEEPER-518.patch


 this is the code in Leader.java 
 {code}
  if (LOG.isDebugEnabled()) {
 LOG.debug(Ack zxid: 0x + Long.toHexString(zxid));
 for (Proposal p : outstandingProposals.values()) {
 long packetZxid = p.packet.getZxid();
 LOG.debug(outstanding proposal: 0x
 + Long.toHexString(packetZxid));
 }
 LOG.debug(outstanding proposals all);
 }
 {code}
 We should move this debug to trace since it will cause really high latencies 
 in response times from zookeeper servers in case folks want to use DEBUG 
 logging for servers.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.