date:20110822

[jira] [Commented] (HBASE-4215) RS requestsPerSecond counter seems to be off

2011-08-22 Thread subramanian raghunathan (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-4215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13088577#comment-13088577
 ] 

subramanian raghunathan commented on HBASE-4215:


1)  Modifying the requestPersecond value to integer rather than float since the 
value is used in several VO's
like: 
1) MasterMetrics metrics 
2) AClusterStatus
3) StorageClusterStatusModel
4) AServerLoad etc. 

Also to maintain consistensy the regionservermetrics and HServerLoad using 
integer values for requestPersecond.

Advantages: Consitency throughout the system . Changes are minimal.
DisAdvantages: Percision loss, also integer can accomadate less value than the 
float.

2)HServerLoad.getNumberOfRequests() is used in multiple places.

{color:green}StorageClusterStatusModel - Expects request per second 
ClusterStatus - Expects request per second 
MasterStatusTmplImpl - UI part also Expects request per second {color}

{color:red}AvroUtil - Not sure {color} 

{color:red}
HMaster 
public void regionServerReport(final byte [] sn, final HServerLoad hsl)
  throws IOException {
this.serverManager.regionServerReport(new ServerName(sn), hsl);
if (hsl != null  this.metrics != null) {
  // Up our metrics.
  this.metrics.incrementRequests(hsl.getTotalNumberOfRequests());
}
  }
The metric expects the total request in the all the region servers and the 
metric computes the per second value of the aggregation of all the region 
servers.{color}

So following change is sugested to keep the existing attribute as the 
requestPersecond.Also introduce additional attribute that reports the total 
request made in RS as totalNumberOfRequests This will be used by the Master 
Metrics.

Will upload the patch ASAP 

 RS requestsPerSecond counter seems to be off
 

 Key: HBASE-4215
 URL: https://issues.apache.org/jira/browse/HBASE-4215
 Project: HBase
  Issue Type: Bug
  Components: metrics
Affects Versions: 0.92.0
Reporter: Todd Lipcon
Assignee: ramkrishna.s.vasudevan
Priority: Critical
 Fix For: 0.92.0


 In testing trunk, I had YCSB reporting some 40,000 requests/second, but the 
 summary info on the master webpage was consistently indicating somewhere 
 around 3x that. I'm guessing that we may have a bug where we forgot to divide 
 by time.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-4229) Replace Jettison JSON encoding with Jackson in HLogPrettyPrinter

2011-08-22 Thread Hudson (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-4229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13088592#comment-13088592
 ] 

Hudson commented on HBASE-4229:
---

Integrated in HBase-TRUNK #2127 (See 
[https://builds.apache.org/job/HBase-TRUNK/2127/])
HBASE-4229 Replace Jettison JSON encoding with Jackson in HLogPrettyPrinter

stack : 
Files : 
* 
/hbase/trunk/src/main/java/org/apache/hadoop/hbase/regionserver/wal/HLogPrettyPrinter.java
* /hbase/trunk/CHANGES.txt
* /hbase/trunk/bin/add_table.rb
* /hbase/trunk/pom.xml


 Replace Jettison JSON encoding with Jackson in HLogPrettyPrinter
 

 Key: HBASE-4229
 URL: https://issues.apache.org/jira/browse/HBASE-4229
 Project: HBase
  Issue Type: Improvement
  Components: wal
Reporter: Riley Patterson
Assignee: Riley Patterson
Priority: Trivial
 Fix For: 0.92.0

 Attachments: HBASE-4229.patch


 HBase makes use of both jackson (in the region server) and jettison (in 
 HLogPrettyPrinter) for JSON encoding. Jackson seems to be better maintained, 
 so this patch standardizes by using jackson in HLogPrettyPrinter instead of 
 jettison.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-4220) Lots of DNS queries from client

2011-08-22 Thread ramkrishna.s.vasudevan (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13088534#comment-13088534
 ] 

ramkrishna.s.vasudevan commented on HBASE-4220:
---

+1 

 Lots of DNS queries from client
 ---

 Key: HBASE-4220
 URL: https://issues.apache.org/jira/browse/HBASE-4220
 Project: HBase
  Issue Type: Bug
  Components: client
Affects Versions: 0.92.0
Reporter: Todd Lipcon
Assignee: stack
Priority: Critical
 Fix For: 0.92.0

 Attachments: 4220.txt


 In running a YCSB workload, I managed to DDOS a DNS server since it seems to 
 be flooding lots of DNS requests. Installing nscd on the client machines 
 improved throughput by a factor of 6 and stopped killing the server. These 
 are long-running clients, so it's not clear why we do so many lookups.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-4230) Compaction threads need names

2011-08-22 Thread Hudson (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-4230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13088593#comment-13088593
 ] 

Hudson commented on HBASE-4230:
---

Integrated in HBase-TRUNK #2127 (See 
[https://builds.apache.org/job/HBase-TRUNK/2127/])
HBASE-4230 Compaction threads need names

apurtell : 
Files : 
* 
/hbase/trunk/src/main/java/org/apache/hadoop/hbase/regionserver/CompactSplitThread.java
* /hbase/trunk/CHANGES.txt


 Compaction threads need names
 -

 Key: HBASE-4230
 URL: https://issues.apache.org/jira/browse/HBASE-4230
 Project: HBase
  Issue Type: Bug
  Components: regionserver
Affects Versions: 0.92.0
Reporter: Todd Lipcon
Assignee: Andrew Purtell
 Fix For: 0.92.0

 Attachments: HBASE-4230.patch


 The CompactSplitThread creates executors for doing compaction work, but 
 threads end up named things like pool-2-thread-1 which isn't very useful.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-4213) Support instant schema updates with out master's intervention (i.e with out enable/disable and bulk assign/unassign)

2011-08-22 Thread Subbu M Iyer (JIRA)


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

Subbu M Iyer updated HBASE-4213:


Attachment: HBASE_Instant_schema_change-version_3_.patch

 Support instant schema updates with out master's intervention (i.e with out 
 enable/disable and bulk assign/unassign)
 

 Key: HBASE-4213
 URL: https://issues.apache.org/jira/browse/HBASE-4213
 Project: HBase
  Issue Type: Improvement
Reporter: Subbu M Iyer
Assignee: Subbu M Iyer
 Fix For: 0.92.0

 Attachments: HBASE-4213-Instant_schema_change.patch, 
 HBASE-4213_Instant_schema_change_-Version_2_.patch, 
 HBASE_Instant_schema_change-version_3_.patch


 This Jira is a slight variation in approach to what is being done as part of 
 https://issues.apache.org/jira/browse/HBASE-1730
 Support instant schema updates such as Modify Table, Add Column, Modify 
 Column operations:
 1. With out enable/disabling the table.
 2. With out bulk unassign/assign of regions.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (HBASE-4225) NoSuchColumnFamilyException in multi doesn't say which family is bad

2011-08-22 Thread ramkrishna.s.vasudevan (JIRA)


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

ramkrishna.s.vasudevan reassigned HBASE-4225:
-

Assignee: ramkrishna.s.vasudevan

 NoSuchColumnFamilyException in multi doesn't say which family is bad
 

 Key: HBASE-4225
 URL: https://issues.apache.org/jira/browse/HBASE-4225
 Project: HBase
  Issue Type: Improvement
Affects Versions: 0.90.4
Reporter: Jean-Daniel Cryans
Assignee: ramkrishna.s.vasudevan
Priority: Critical
 Fix For: 0.90.5


 It's kind of a dumb one, in HRegion.doMiniBatchPut we do:
 {code}
 LOG.warn(No such column family in batch put, nscf);
 batchOp.retCodes[lastIndexExclusive] = OperationStatusCode.BAD_FAMILY;
 {code}
 So we lose the family here, all we know is there's a bad one, that's what's 
 in HRS.multi:
 {code}
 } else if (code == OperationStatusCode.BAD_FAMILY) {
   result = new NoSuchColumnFamilyException();
 {code}
 We can't just throw the exception like that, we need to say which one is bad 
 even if it requires testing all passed MultiActions.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-4213) Support instant schema updates with out master's intervention (i.e with out enable/disable and bulk assign/unassign)

2011-08-22 Thread Subbu M Iyer (JIRA)

[
https://issues.apache.org/jira/browse/HBASE-4213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13088462#comment-13088462
]

Subbu M Iyer commented on HBASE-4213:
-

Latest patch includes the following changes:

1. Load balancer will be turned off (if already enabled) before an instant
schema change operation.
2. Load balancer will be turned on (if was on before the instant schema change).
3. Added a ZK based check instead of sleep timer for couple of tests.
4. Master stores the number of online RS while creating the schema change node.
On completion the master compares against this count (rather than current
number of active RS which might have changed during the schema change
operation) with number of active RS to determine if all the RS have completed
the schema change operation.

Support instant schema updates with out master's intervention (i.e with out
enable/disable and bulk assign/unassign)

Key: HBASE-4213
URL: https://issues.apache.org/jira/browse/HBASE-4213
Project: HBase
Issue Type: Improvement
Reporter: Subbu M Iyer
Assignee: Subbu M Iyer
Fix For: 0.92.0

Attachments: HBASE-4213-Instant_schema_change.patch,
HBASE-4213_Instant_schema_change_-Version_2_.patch,
HBASE_Instant_schema_change-version_3_.patch

This Jira is a slight variation in approach to what is being done as part of
https://issues.apache.org/jira/browse/HBASE-1730
Support instant schema updates such as Modify Table, Add Column, Modify
Column operations:
1. With out enable/disabling the table.
2. With out bulk unassign/assign of regions.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

73 matches

Mail list logo