[jira] [Updated] (HBASE-12912) StoreScanner calls Configuration for Boolean Check on each initialization
[ https://issues.apache.org/jira/browse/HBASE-12912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-12912: --- Issue Type: Sub-task (was: Bug) Parent: HBASE-14266 > StoreScanner calls Configuration for Boolean Check on each initialization > - > > Key: HBASE-12912 > URL: https://issues.apache.org/jira/browse/HBASE-12912 > Project: HBase > Issue Type: Sub-task >Reporter: John Leach >Assignee: John Leach > Fix For: 2.0.0, 1.3.0, 0.98.16 > > Attachments: StoreScannerStall.tiff > > Original Estimate: 1h > Remaining Estimate: 1h > > There is a clear CPU drain and iterator creation when creating store scanners > under high load. Splice was running a TPCC test of our database and we are > seeing object creation and CPU waste on the boolean check > Code Snippet... > if (store != null && ((HStore)store).getHRegion() != null > && store.getStorefilesCount() > 1) { > RegionServerServices rsService = > ((HStore)store).getHRegion().getRegionServerServices(); > if (rsService == null || !rsService.getConfiguration().getBoolean( > STORESCANNER_PARALLEL_SEEK_ENABLE, false)) return; > isParallelSeekEnabled = true; > executor = rsService.getExecutorService(); > } > Will attach profile... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12912) StoreScanner calls Configuration for Boolean Check on each initialization
[ https://issues.apache.org/jira/browse/HBASE-12912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-12912: --- Fix Version/s: (was: 0.98.15) 0.98.16 > StoreScanner calls Configuration for Boolean Check on each initialization > - > > Key: HBASE-12912 > URL: https://issues.apache.org/jira/browse/HBASE-12912 > Project: HBase > Issue Type: Bug >Reporter: John Leach >Assignee: John Leach > Fix For: 2.0.0, 1.3.0, 0.98.16 > > Attachments: StoreScannerStall.tiff > > Original Estimate: 1h > Remaining Estimate: 1h > > There is a clear CPU drain and iterator creation when creating store scanners > under high load. Splice was running a TPCC test of our database and we are > seeing object creation and CPU waste on the boolean check > Code Snippet... > if (store != null && ((HStore)store).getHRegion() != null > && store.getStorefilesCount() > 1) { > RegionServerServices rsService = > ((HStore)store).getHRegion().getRegionServerServices(); > if (rsService == null || !rsService.getConfiguration().getBoolean( > STORESCANNER_PARALLEL_SEEK_ENABLE, false)) return; > isParallelSeekEnabled = true; > executor = rsService.getExecutorService(); > } > Will attach profile... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12912) StoreScanner calls Configuration for Boolean Check on each initialization
[ https://issues.apache.org/jira/browse/HBASE-12912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-12912: --- Fix Version/s: (was: 1.1.3) (was: 1.0.3) (was: 1.2.1) (was: 0.98.14) 0.98.15 StoreScanner calls Configuration for Boolean Check on each initialization - Key: HBASE-12912 URL: https://issues.apache.org/jira/browse/HBASE-12912 Project: HBase Issue Type: Bug Reporter: John Leach Assignee: John Leach Fix For: 2.0.0, 1.3.0, 0.98.15 Attachments: StoreScannerStall.tiff Original Estimate: 1h Remaining Estimate: 1h There is a clear CPU drain and iterator creation when creating store scanners under high load. Splice was running a TPCC test of our database and we are seeing object creation and CPU waste on the boolean check Code Snippet... if (store != null ((HStore)store).getHRegion() != null store.getStorefilesCount() 1) { RegionServerServices rsService = ((HStore)store).getHRegion().getRegionServerServices(); if (rsService == null || !rsService.getConfiguration().getBoolean( STORESCANNER_PARALLEL_SEEK_ENABLE, false)) return; isParallelSeekEnabled = true; executor = rsService.getExecutorService(); } Will attach profile... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12912) StoreScanner calls Configuration for Boolean Check on each initialization
[ https://issues.apache.org/jira/browse/HBASE-12912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Dimiduk updated HBASE-12912: - Fix Version/s: (was: 1.1.2) 1.1.3 StoreScanner calls Configuration for Boolean Check on each initialization - Key: HBASE-12912 URL: https://issues.apache.org/jira/browse/HBASE-12912 Project: HBase Issue Type: Bug Reporter: John Leach Assignee: John Leach Fix For: 2.0.0, 0.98.14, 1.3.0, 1.2.1, 1.0.3, 1.1.3 Attachments: StoreScannerStall.tiff Original Estimate: 1h Remaining Estimate: 1h There is a clear CPU drain and iterator creation when creating store scanners under high load. Splice was running a TPCC test of our database and we are seeing object creation and CPU waste on the boolean check Code Snippet... if (store != null ((HStore)store).getHRegion() != null store.getStorefilesCount() 1) { RegionServerServices rsService = ((HStore)store).getHRegion().getRegionServerServices(); if (rsService == null || !rsService.getConfiguration().getBoolean( STORESCANNER_PARALLEL_SEEK_ENABLE, false)) return; isParallelSeekEnabled = true; executor = rsService.getExecutorService(); } Will attach profile... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12912) StoreScanner calls Configuration for Boolean Check on each initialization
[ https://issues.apache.org/jira/browse/HBASE-12912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Busbey updated HBASE-12912: Fix Version/s: (was: 1.2.0) 1.2.1 1.3.0 Still working on this [~jleach], or would you prefer we have someone else get a patch together? StoreScanner calls Configuration for Boolean Check on each initialization - Key: HBASE-12912 URL: https://issues.apache.org/jira/browse/HBASE-12912 Project: HBase Issue Type: Bug Reporter: John Leach Assignee: John Leach Fix For: 2.0.0, 0.98.14, 1.0.2, 1.1.2, 1.3.0, 1.2.1 Attachments: StoreScannerStall.tiff Original Estimate: 1h Remaining Estimate: 1h There is a clear CPU drain and iterator creation when creating store scanners under high load. Splice was running a TPCC test of our database and we are seeing object creation and CPU waste on the boolean check Code Snippet... if (store != null ((HStore)store).getHRegion() != null store.getStorefilesCount() 1) { RegionServerServices rsService = ((HStore)store).getHRegion().getRegionServerServices(); if (rsService == null || !rsService.getConfiguration().getBoolean( STORESCANNER_PARALLEL_SEEK_ENABLE, false)) return; isParallelSeekEnabled = true; executor = rsService.getExecutorService(); } Will attach profile... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12912) StoreScanner calls Configuration for Boolean Check on each initialization
[ https://issues.apache.org/jira/browse/HBASE-12912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Enis Soztutar updated HBASE-12912: -- Fix Version/s: (was: 1.0.2) 1.0.3 StoreScanner calls Configuration for Boolean Check on each initialization - Key: HBASE-12912 URL: https://issues.apache.org/jira/browse/HBASE-12912 Project: HBase Issue Type: Bug Reporter: John Leach Assignee: John Leach Fix For: 2.0.0, 0.98.14, 1.1.2, 1.3.0, 1.2.1, 1.0.3 Attachments: StoreScannerStall.tiff Original Estimate: 1h Remaining Estimate: 1h There is a clear CPU drain and iterator creation when creating store scanners under high load. Splice was running a TPCC test of our database and we are seeing object creation and CPU waste on the boolean check Code Snippet... if (store != null ((HStore)store).getHRegion() != null store.getStorefilesCount() 1) { RegionServerServices rsService = ((HStore)store).getHRegion().getRegionServerServices(); if (rsService == null || !rsService.getConfiguration().getBoolean( STORESCANNER_PARALLEL_SEEK_ENABLE, false)) return; isParallelSeekEnabled = true; executor = rsService.getExecutorService(); } Will attach profile... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12912) StoreScanner calls Configuration for Boolean Check on each initialization
[ https://issues.apache.org/jira/browse/HBASE-12912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Dimiduk updated HBASE-12912: - Fix Version/s: (was: 1.1.1) 1.1.2 StoreScanner calls Configuration for Boolean Check on each initialization - Key: HBASE-12912 URL: https://issues.apache.org/jira/browse/HBASE-12912 Project: HBase Issue Type: Bug Reporter: John Leach Assignee: John Leach Fix For: 2.0.0, 0.98.14, 1.0.2, 1.2.0, 1.1.2 Attachments: StoreScannerStall.tiff Original Estimate: 1h Remaining Estimate: 1h There is a clear CPU drain and iterator creation when creating store scanners under high load. Splice was running a TPCC test of our database and we are seeing object creation and CPU waste on the boolean check Code Snippet... if (store != null ((HStore)store).getHRegion() != null store.getStorefilesCount() 1) { RegionServerServices rsService = ((HStore)store).getHRegion().getRegionServerServices(); if (rsService == null || !rsService.getConfiguration().getBoolean( STORESCANNER_PARALLEL_SEEK_ENABLE, false)) return; isParallelSeekEnabled = true; executor = rsService.getExecutorService(); } Will attach profile... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12912) StoreScanner calls Configuration for Boolean Check on each initialization
[ https://issues.apache.org/jira/browse/HBASE-12912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-12912: --- Fix Version/s: (was: 0.98.13) 0.98.14 StoreScanner calls Configuration for Boolean Check on each initialization - Key: HBASE-12912 URL: https://issues.apache.org/jira/browse/HBASE-12912 Project: HBase Issue Type: Bug Reporter: John Leach Assignee: John Leach Fix For: 2.0.0, 0.98.14, 1.0.2, 1.2.0, 1.1.1 Attachments: StoreScannerStall.tiff Original Estimate: 1h Remaining Estimate: 1h There is a clear CPU drain and iterator creation when creating store scanners under high load. Splice was running a TPCC test of our database and we are seeing object creation and CPU waste on the boolean check Code Snippet... if (store != null ((HStore)store).getHRegion() != null store.getStorefilesCount() 1) { RegionServerServices rsService = ((HStore)store).getHRegion().getRegionServerServices(); if (rsService == null || !rsService.getConfiguration().getBoolean( STORESCANNER_PARALLEL_SEEK_ENABLE, false)) return; isParallelSeekEnabled = true; executor = rsService.getExecutorService(); } Will attach profile... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12912) StoreScanner calls Configuration for Boolean Check on each initialization
[ https://issues.apache.org/jira/browse/HBASE-12912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Dimiduk updated HBASE-12912: - Fix Version/s: (was: 1.1.0) 1.1.1 1.2.0 StoreScanner calls Configuration for Boolean Check on each initialization - Key: HBASE-12912 URL: https://issues.apache.org/jira/browse/HBASE-12912 Project: HBase Issue Type: Bug Reporter: John Leach Assignee: John Leach Fix For: 2.0.0, 0.98.13, 1.0.2, 1.2.0, 1.1.1 Attachments: StoreScannerStall.tiff Original Estimate: 1h Remaining Estimate: 1h There is a clear CPU drain and iterator creation when creating store scanners under high load. Splice was running a TPCC test of our database and we are seeing object creation and CPU waste on the boolean check Code Snippet... if (store != null ((HStore)store).getHRegion() != null store.getStorefilesCount() 1) { RegionServerServices rsService = ((HStore)store).getHRegion().getRegionServerServices(); if (rsService == null || !rsService.getConfiguration().getBoolean( STORESCANNER_PARALLEL_SEEK_ENABLE, false)) return; isParallelSeekEnabled = true; executor = rsService.getExecutorService(); } Will attach profile... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12912) StoreScanner calls Configuration for Boolean Check on each initialization
[ https://issues.apache.org/jira/browse/HBASE-12912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Enis Soztutar updated HBASE-12912: -- Fix Version/s: (was: 1.0.1) 1.0.2 StoreScanner calls Configuration for Boolean Check on each initialization - Key: HBASE-12912 URL: https://issues.apache.org/jira/browse/HBASE-12912 Project: HBase Issue Type: Bug Reporter: John Leach Assignee: John Leach Fix For: 2.0.0, 1.1.0, 0.98.13, 1.0.2 Attachments: StoreScannerStall.tiff Original Estimate: 1h Remaining Estimate: 1h There is a clear CPU drain and iterator creation when creating store scanners under high load. Splice was running a TPCC test of our database and we are seeing object creation and CPU waste on the boolean check Code Snippet... if (store != null ((HStore)store).getHRegion() != null store.getStorefilesCount() 1) { RegionServerServices rsService = ((HStore)store).getHRegion().getRegionServerServices(); if (rsService == null || !rsService.getConfiguration().getBoolean( STORESCANNER_PARALLEL_SEEK_ENABLE, false)) return; isParallelSeekEnabled = true; executor = rsService.getExecutorService(); } Will attach profile... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12912) StoreScanner calls Configuration for Boolean Check on each initialization
[ https://issues.apache.org/jira/browse/HBASE-12912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-12912: --- Fix Version/s: (was: 0.98.12) 0.98.13 StoreScanner calls Configuration for Boolean Check on each initialization - Key: HBASE-12912 URL: https://issues.apache.org/jira/browse/HBASE-12912 Project: HBase Issue Type: Bug Reporter: John Leach Assignee: John Leach Fix For: 2.0.0, 1.0.1, 1.1.0, 0.98.13 Attachments: StoreScannerStall.tiff Original Estimate: 1h Remaining Estimate: 1h There is a clear CPU drain and iterator creation when creating store scanners under high load. Splice was running a TPCC test of our database and we are seeing object creation and CPU waste on the boolean check Code Snippet... if (store != null ((HStore)store).getHRegion() != null store.getStorefilesCount() 1) { RegionServerServices rsService = ((HStore)store).getHRegion().getRegionServerServices(); if (rsService == null || !rsService.getConfiguration().getBoolean( STORESCANNER_PARALLEL_SEEK_ENABLE, false)) return; isParallelSeekEnabled = true; executor = rsService.getExecutorService(); } Will attach profile... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12912) StoreScanner calls Configuration for Boolean Check on each initialization
[ https://issues.apache.org/jira/browse/HBASE-12912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-12912: --- Fix Version/s: (was: 0.98.11) 0.98.12 Moved out to 0.98.12 StoreScanner calls Configuration for Boolean Check on each initialization - Key: HBASE-12912 URL: https://issues.apache.org/jira/browse/HBASE-12912 Project: HBase Issue Type: Bug Reporter: John Leach Assignee: John Leach Fix For: 2.0.0, 1.0.1, 1.1.0, 0.98.12 Attachments: StoreScannerStall.tiff Original Estimate: 1h Remaining Estimate: 1h There is a clear CPU drain and iterator creation when creating store scanners under high load. Splice was running a TPCC test of our database and we are seeing object creation and CPU waste on the boolean check Code Snippet... if (store != null ((HStore)store).getHRegion() != null store.getStorefilesCount() 1) { RegionServerServices rsService = ((HStore)store).getHRegion().getRegionServerServices(); if (rsService == null || !rsService.getConfiguration().getBoolean( STORESCANNER_PARALLEL_SEEK_ENABLE, false)) return; isParallelSeekEnabled = true; executor = rsService.getExecutorService(); } Will attach profile... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12912) StoreScanner calls Configuration for Boolean Check on each initialization
[ https://issues.apache.org/jira/browse/HBASE-12912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-12912: --- Fix Version/s: (was: 0.98.10) 0.98.11 StoreScanner calls Configuration for Boolean Check on each initialization - Key: HBASE-12912 URL: https://issues.apache.org/jira/browse/HBASE-12912 Project: HBase Issue Type: Bug Reporter: John Leach Assignee: John Leach Fix For: 1.0.0, 2.0.0, 1.1.0, 0.98.11 Attachments: StoreScannerStall.tiff Original Estimate: 1h Remaining Estimate: 1h There is a clear CPU drain and iterator creation when creating store scanners under high load. Splice was running a TPCC test of our database and we are seeing object creation and CPU waste on the boolean check Code Snippet... if (store != null ((HStore)store).getHRegion() != null store.getStorefilesCount() 1) { RegionServerServices rsService = ((HStore)store).getHRegion().getRegionServerServices(); if (rsService == null || !rsService.getConfiguration().getBoolean( STORESCANNER_PARALLEL_SEEK_ENABLE, false)) return; isParallelSeekEnabled = true; executor = rsService.getExecutorService(); } Will attach profile... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12912) StoreScanner calls Configuration for Boolean Check on each initialization
[ https://issues.apache.org/jira/browse/HBASE-12912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Enis Soztutar updated HBASE-12912: -- Fix Version/s: (was: 1.0.0) 1.0.1 StoreScanner calls Configuration for Boolean Check on each initialization - Key: HBASE-12912 URL: https://issues.apache.org/jira/browse/HBASE-12912 Project: HBase Issue Type: Bug Reporter: John Leach Assignee: John Leach Fix For: 2.0.0, 1.0.1, 1.1.0, 0.98.11 Attachments: StoreScannerStall.tiff Original Estimate: 1h Remaining Estimate: 1h There is a clear CPU drain and iterator creation when creating store scanners under high load. Splice was running a TPCC test of our database and we are seeing object creation and CPU waste on the boolean check Code Snippet... if (store != null ((HStore)store).getHRegion() != null store.getStorefilesCount() 1) { RegionServerServices rsService = ((HStore)store).getHRegion().getRegionServerServices(); if (rsService == null || !rsService.getConfiguration().getBoolean( STORESCANNER_PARALLEL_SEEK_ENABLE, false)) return; isParallelSeekEnabled = true; executor = rsService.getExecutorService(); } Will attach profile... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12912) StoreScanner calls Configuration for Boolean Check on each initialization
[ https://issues.apache.org/jira/browse/HBASE-12912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Leach updated HBASE-12912: --- Attachment: StoreScannerStall.tiff A picture of the CPU effect of the boolean check... StoreScanner calls Configuration for Boolean Check on each initialization - Key: HBASE-12912 URL: https://issues.apache.org/jira/browse/HBASE-12912 Project: HBase Issue Type: Bug Reporter: John Leach Attachments: StoreScannerStall.tiff Original Estimate: 1h Remaining Estimate: 1h There is a clear CPU drain and iterator creation when creating store scanners under high load. Splice was running a TPCC test of our database and we are seeing object creation and CPU waste on the boolean check Code Snippet... if (store != null ((HStore)store).getHRegion() != null store.getStorefilesCount() 1) { RegionServerServices rsService = ((HStore)store).getHRegion().getRegionServerServices(); if (rsService == null || !rsService.getConfiguration().getBoolean( STORESCANNER_PARALLEL_SEEK_ENABLE, false)) return; isParallelSeekEnabled = true; executor = rsService.getExecutorService(); } Will attach profile... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12912) StoreScanner calls Configuration for Boolean Check on each initialization
[ https://issues.apache.org/jira/browse/HBASE-12912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-12912: --- Fix Version/s: 1.1.0 0.98.10 2.0.0 1.0.0 Thanks, let me look into it. If one of your guys has a patch [~jleach], I'll be happy to reassign. StoreScanner calls Configuration for Boolean Check on each initialization - Key: HBASE-12912 URL: https://issues.apache.org/jira/browse/HBASE-12912 Project: HBase Issue Type: Bug Reporter: John Leach Assignee: Andrew Purtell Fix For: 1.0.0, 2.0.0, 0.98.10, 1.1.0 Attachments: StoreScannerStall.tiff Original Estimate: 1h Remaining Estimate: 1h There is a clear CPU drain and iterator creation when creating store scanners under high load. Splice was running a TPCC test of our database and we are seeing object creation and CPU waste on the boolean check Code Snippet... if (store != null ((HStore)store).getHRegion() != null store.getStorefilesCount() 1) { RegionServerServices rsService = ((HStore)store).getHRegion().getRegionServerServices(); if (rsService == null || !rsService.getConfiguration().getBoolean( STORESCANNER_PARALLEL_SEEK_ENABLE, false)) return; isParallelSeekEnabled = true; executor = rsService.getExecutorService(); } Will attach profile... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12912) StoreScanner calls Configuration for Boolean Check on each initialization
[ https://issues.apache.org/jira/browse/HBASE-12912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-12912: --- Assignee: John Leach (was: Andrew Purtell) Reassigned as requested, thanks! StoreScanner calls Configuration for Boolean Check on each initialization - Key: HBASE-12912 URL: https://issues.apache.org/jira/browse/HBASE-12912 Project: HBase Issue Type: Bug Reporter: John Leach Assignee: John Leach Fix For: 1.0.0, 2.0.0, 0.98.10, 1.1.0 Attachments: StoreScannerStall.tiff Original Estimate: 1h Remaining Estimate: 1h There is a clear CPU drain and iterator creation when creating store scanners under high load. Splice was running a TPCC test of our database and we are seeing object creation and CPU waste on the boolean check Code Snippet... if (store != null ((HStore)store).getHRegion() != null store.getStorefilesCount() 1) { RegionServerServices rsService = ((HStore)store).getHRegion().getRegionServerServices(); if (rsService == null || !rsService.getConfiguration().getBoolean( STORESCANNER_PARALLEL_SEEK_ENABLE, false)) return; isParallelSeekEnabled = true; executor = rsService.getExecutorService(); } Will attach profile... -- This message was sent by Atlassian JIRA (v6.3.4#6332)