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

Keith Turner updated ACCUMULO-4798:
-----------------------------------
    Description: 
The ZooKeeper cache code caches Zookeeper stats.  When a stat is requested from 
the cache it copies it.  The ZK stat class offers no good way to copy other 
than serialize and deserialize.  The code currently does this and its slow.  
All code in Accumulo only uses one field from stat, so it would be much better 
to create a simple class that has this one field and can quickly copy.  

 

The stat is used very frequently in the metadata cache code to check if a 
tserver still holds its lock.

 

  was:The ZooKeeper cache code caches Zookeeper stats.  When a stat is 
requested from the cache it copies it.  The ZK stat class offers no good way to 
copy other than serialize and deserialize.  The code currently does this and 
its slow.  All code in Accumulo only uses one field from stat, so it would be 
much better to create a simple class that has this one field and can quickly 
copy.  


> Copying Stat in ZooCache is slow
> --------------------------------
>
>                 Key: ACCUMULO-4798
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-4798
>             Project: Accumulo
>          Issue Type: Improvement
>    Affects Versions: 1.7.3, 1.8.1
>            Reporter: Keith Turner
>            Priority: Major
>             Fix For: 1.9.0, 2.0.0
>
>
> The ZooKeeper cache code caches Zookeeper stats.  When a stat is requested 
> from the cache it copies it.  The ZK stat class offers no good way to copy 
> other than serialize and deserialize.  The code currently does this and its 
> slow.  All code in Accumulo only uses one field from stat, so it would be 
> much better to create a simple class that has this one field and can quickly 
> copy.  
>  
> The stat is used very frequently in the metadata cache code to check if a 
> tserver still holds its lock.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to