accumulo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From els...@apache.org
Subject svn commit: r1687829 - /accumulo/site/trunk/content/release_notes/1.5.3.mdtext
Date Fri, 26 Jun 2015 18:27:59 GMT
Author: elserj
Date: Fri Jun 26 18:27:59 2015
New Revision: 1687829

URL: http://svn.apache.org/r1687829
Log:
Consistently link JIRA issues and add missing anchor definition

Modified:
    accumulo/site/trunk/content/release_notes/1.5.3.mdtext

Modified: accumulo/site/trunk/content/release_notes/1.5.3.mdtext
URL: http://svn.apache.org/viewvc/accumulo/site/trunk/content/release_notes/1.5.3.mdtext?rev=1687829&r1=1687828&r2=1687829&view=diff
==============================================================================
--- accumulo/site/trunk/content/release_notes/1.5.3.mdtext (original)
+++ accumulo/site/trunk/content/release_notes/1.5.3.mdtext Fri Jun 26 18:27:59 2015
@@ -49,7 +49,7 @@ whether data for a tablet read from memo
 compaction), was found deadlocked in a production system.
 
 This deadlock prevented the scan and the minor compaction from ever successfully completing
-without restarting the tablet server. ACCUMULO-3745 fixes the inconsistent synchronization
+without restarting the tablet server. [ACCUMULO-3745] fixes the inconsistent synchronization
 inside of the SourceSwitchingIterator to prevent this deadlock from happening in the future.
 
 The only mitigation of this bug was to restart the tablet server that is deadlocked.
@@ -66,7 +66,7 @@ a deadlock occurred.
 This deadlock happened because the synchronous flush call could not complete before the load
 tablet call completed, but the load tablet call couldn't run because of connection caching
we
 perform in Accumulo's RPC layer to reduce the quantity of sockets we need to create to send
data.
-ACCUMULO-3597 prevents this deadlock by forcing the use of a non-cached connection for the
RPC
+[ACCUMULO-3597] prevents this deadlock by forcing the use of a non-cached connection for
the RPC
 message requesting a metadata tablet to be loaded.
 
 While this feature does result in additional network resources to be used, the concern is
minimal
@@ -136,6 +136,7 @@ Accumulo configuration from `120s` to `2
 </table>
 
 [ACCUMULO-3316]: https://issues.apache.org/jira/browse/ACCUMULO-3316
+[ACCUMULO-3317]: https://issues.apache.org/jira/browse/ACCUMULO-3317
 [ACCUMULO-2388]: https://issues.apache.org/jira/browse/ACCUMULO-2388
 [ACCUMULO-3474]: https://issues.apache.org/jira/browse/ACCUMULO-3474
 [ACCUMULO-3574]: https://issues.apache.org/jira/browse/ACCUMULO-3574



Mime
View raw message