Search Hadoop -
Colin Patrick McCabe
Arun C Murthy
Tsz Wo Nicholas Sze
Brahma Reddy Battula
Robert Joseph Evans
mail # user
last 7 days (5)
last 30 days (5)
last 90 days (12)
last 6 months (22)
last 9 months (124)
and all its subprojects:
newest on top
oldest on top
. Results from
Loading phrases to help you
refine your search...
[HADOOP-13442] Optimize UGI group lookups
...UGI#getGroups and its usage is inefficient. The list is unnecessarily converted to multiple collections.For every invocation, the List<String> from the group provider is converte...
, 2016-07-29, 19:15
[HADOOP-13426] More efficiently build IPC responses
...The call response buffer is allowed to dynamically grow until a max size is reached. Often times the full size of the response can be known in advance which avoids copies. This i...
, 2016-07-29, 15:37
[HADOOP-13438] Optimize IPC server protobuf decoding
...The current use of the protobuf API uses an expensive code path. The builder uses the parser to instantiate a message, then copies the message into the builder. The parser is cre...
, 2016-07-28, 22:08
[HADOOP-13429] Dispose of unnecessary SASL servers
...The IPC server retains a per-connection SASL server for the duration of the connection. This causes many unnecessary objects to be promoted to old gen. The SASL server should be ...
, 2016-07-28, 21:44
[HADOOP-13425] IPC layer optimizations
...Umbrella jira for y! optimizations to reduce object allocations, more efficiently use protobuf APIs, unified ipc and webhdfs callq to enable QoS, etc....
, 2016-07-26, 17:21
[HADOOP-9956] RPC listener inefficiently assigns connections to readers
...The socket listener and readers use a complex synchronization to update the reader's NIO Selector. Updating active selectors is not thread-safe so precautions are required.However, the...
, 2016-06-08, 03:28
[HADOOP-10940] RPC client does no bounds checking of responses
...The rpc client does no bounds checking of server responses. In the case of communicating with an older and incompatible RPC, this may lead to OOM issues and leaking of resources....
, 2016-06-05, 05:53
[HADOOP-10014] Symlink resolution is fundamentally broken for multi-layered filesystems
...Symlink resolution is performed on a per-filesystem basis. In a multi-layered filesystem, the symlinks need to be resolved relative to the highest level filesystem in the stack. ...
, 2016-06-05, 05:51
[HADOOP-9749] Remove synchronization for UGI.getCurrentUser
...HADOOP-7854 added synchronization to getCurrentUser due to ConcurrentModificationExceptions. This degrades NN call handler performance.The problem was not well understood at the time, ...
, 2016-06-05, 05:50
[HADOOP-9747] Reduce unnecessary UGI synchronization
...Jstacks of heavily loaded NNs show up to dozens of threads blocking in the UGI....
, 2016-06-05, 05:50
Apache Lucene, Apache Solr and all other Apache Software Foundation projects and their respective logos are trademarks of the Apache Software Foundation.
Elasticsearch, Kibana, Logstash, and Beats are trademarks of Elasticsearch BV, registered in the U.S. and in other countries. This site and Sematext Group is in no way affiliated with Elasticsearch BV.
Service operated by