25 Apr, 2014

2 commits

  • - Moved dsconfig package to opendj-config.
    -> Several checkstyle errors still exist and will be fixed after this commit in order to let the changes on main files more readable.
    -> BuildVersion.java will be renamed, moved later.
    
    
    ** DsConfig.java
    - Added logger.
    - Removed checkVersionMismatch and moved it to LDAPManagementContextFactory where the connection is opened.
    
    ** BuildVersion.java
    - Added function to get the current configuration entry value of "cn=Version,cn=monitor"
    
    ** LDAPManagementContextFactory.java
    - Added checkVersionMismatch.
    
    **config.properties
    - Added messages linked to BuildVersion.
    
    ** SDK *check* style modifications on :
    - PropertyEditorModification.java
    - PropertyValueEditor.java
    - HelpSubCommandHandler.java
    - SetPropSubCommandHandler.java
    - SubCommandHandler.java
    - ListSubCommandHandler.java
    - CreateSubCommandHandler.java
    - PropertyValuePrinter.java
    - DeleteSubCommandHandler.java
    - SubCommandHandlerFactory.java
    - ArgumentExceptionFactory.java
    - GetPropSubCommandHandler.java
    - CLIProfile.java
    
    ** pom file : added dependency on opendj-cli.
    
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@10676 41b1ffd8-f28e-4786-ab96-9950f0a78031
    violette
     
  • Thanks, Chris Ridd!
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@10675 41b1ffd8-f28e-4786-ab96-9950f0a78031
    mark
     

24 Apr, 2014

3 commits


23 Apr, 2014

2 commits

  • Preliminary work, also needed by Nicolas for OPENDJ-1177.
    
    
    ByteSequenceReader.java:
    Added peek() and peek(int offset).
    
    ByteSequenceReaderTest.java:
    Added a test.
    Added method b() to ease reading in int -> byte conversion.
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@10670 41b1ffd8-f28e-4786-ab96-9950f0a78031
    JnRouvignac
     
  • It seems unnecessary to have a msgQueue on top of JE since JE's already has a builtin cache that handles the same responsibility.
    This improvement removes the JEReplicaDB.msgQueue and the associated flushing thread to save on memory and resources.
    
    Code cleanup in JEChangeNumberIndexDB after CR-3388.
    
    
    JEReplicaDB.java:
    Does not implement Runnable anymore.
    Removed fields msgQueue, queueSizeBytes, queueMaxBytes, thread, flushLock.
    Added and used shutdown field to compensate for removing the thread field.
    Removed methods collectAllPermits(), flush(), run() and stop().
    In shutdown(), used AtomicBoolean.compareAndSet().
    
    ReplicationDB.java:
    Renamed addEntries(List<UpdateMsg>) to addEntry(UpdateMsg).
    
    JEReplicaDBTest.java:
    Removed now unnecessary waitChangesArePersisted().
    
    
    JEChangelogDB.java:
    In shutdown(), enforced threads joining + called Thread.interrupt() to ensure shutdown. This prevents message about unclosed cursors in integrated unit tests.
    
    ReplicationServer.java:
    Removed getQueueSize().
    
    
    JEChangeNumberIndexDB.java:
    Removed unused oldestChangeNumber.
    In shutdown(), used AtomicBoolean.compareAndSet() + removed useless call to notify().
    
    JEChangeNumberIndexDBTest.java:
    Fixed javadocs.
    
    
    ChangeTimeHeartbeatMsg.java:
    Implemented toString().
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@10669 41b1ffd8-f28e-4786-ab96-9950f0a78031
    JnRouvignac
     

18 Apr, 2014

1 commit

  • The bug was due to a very complex interaction between various components. Here is a scenario and explanation:
    1- the change number indexer has no more records to proceed, because all cursors are exhausted, so it calls wait().
    2- a new change Upd1 comes in for an exhausted cursor, medium consistency cannot move.
    3- a new change Upd2 comes in for a cursor that is not already opened, medium consistency can move, so wake up the change number indexer.
    3- on wake up, the change number indexer calls next(), advancing the CompositeDBCursor, which recycles the exhausted cursor, then calls next() on it, making it lose its change. CompositeDBCursor currentRecord == Upd1.
    4- on the next iteration of the loop in run(), a new cursor is created, triggering the creation of a new CompositeDBCursor => Upd1 is lost. CompositeDBCursor currentRecord == Upd2.
    
    The problem comes from two parts:
    - CompositeDBCursor consumes next change from a cursor (which completely forget about this change) and stores it itself
    - ChangeNumberIndexer manages recycling/creating cursors on its own and recreates CompositeDBCursor when a new cursor is created.
    
    The fix required:
    - Preventing CompositeDBCursor from consuming changes from underlying cursors until it can forget about this same change itself.
    - Ensuring only ChangeNumberIndexer handle recycling the cursors it owns instead of having both CompositeDBCursor and ChangeNumberIndexer trying to do it. It is also more performant to let ChangeNumberIndexer manage its cursors.
    
    
    
    CompositeDBCursor.java:
    Added recycleExhaustedCursors field to tell the composite whether it can recycle the cursors itself or not (recycling the cursors is currently needed for persistent searches on the changelog, maybe will we be able to remove it in the future, that would simplify the code a lot).
    Modified the ctor to pass in value of recycleExhaustedCursors.
    Removed currentRecord and currentData fields, replaced by reading the record and field on the first entry in the cursors SortedMap.
    Added state field to ensure the first call to next() does not consume the first change in the cursors SortedMap.
    
    ChangeNumberIndexer.java:
    ChangeNumberIndexer now manages alone the cursors recycling and creation and recreates the CompositeDBCursor when needed.
    In run(), removed the now unneeded call to next() after the wait.
    Added recycleExhaustedCursors().
    
    JEChangelogDB.java:
    Consequence of the change to CompositeDBCursor. Kept old recycling behaviour.
    
    
    ChangeNumberIndexerTest.java:
    Added emptyDBTwoDSsDoesNotLoseChanges() to cover the case being fixed by current commit.
    Renamed test methods dropping the "Initial" when it was not adding much to the test comprehension.
    
    CompositeDBCursorTest.java:
    In newUpdateMsg(), added toString() implementation to help debug.
    Removed recycleTwoElementCursorsTODOJNR().
    In recycleTwoElementCursors(), changed the tests a bit to match the changes to CompositeDBCursor.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@10667 41b1ffd8-f28e-4786-ab96-9950f0a78031
    JnRouvignac
     

17 Apr, 2014

2 commits

  • …beat from known replicas
    
    On startup, if a replication server knows about several replicas, then it must wait to receive some sort of alive information for each of them before being able to move the medium consistency forward.
    Changes or heartbeats received after replication server started are acceptable.
    Likewise, changes that would have been received before the replication server stopped are also acceptable.
    
    This was fixed on replication server startup, by initializing the lastAliveCSN for each known replica, with the oldest possible CSN (timestamp == 0).
    Then when checking if the medium consistency can move forward, if no medium consistency is set, then the lastAliveCSN for each known replica must have a timestamp != 0.
    
    
    ChangeNumberIndexer.java:
    In canMoveForwardMediumConsistencyPoint(), call allInitialReplicasArePastOldestPossibleCSN() if the medium consistency CSN is not set.
    Added methods oldestPossibleCSN(), allInitialReplicasAreAlive().
    
    ChangeNumberIndexerTest.java:
    In emptyDBTwoInitialDSs(), slightly modified the code to test current bug.
    In startCNIndexer(), added the initial ECL enabled domains as a parameter.
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@10666 41b1ffd8-f28e-4786-ab96-9950f0a78031
    JnRouvignac
     
  • The changeNumber progression was blocked when the mediumConsistencyCSN was from a different baseDN than the new change to add to the changeNumber index DB.
    Fixed this problem by also storing the baseDN of the mediumConsistencyCSN in the ChangeNumberIndexer class.
    
    
    ChangeNumberIndexer.java:
    Renamed mediumConsistencyCSN to mediumConsistency and changed its type from CSN to Pair<DN, CSN>.
    In tryNotify(), removed the now useless baseDN parameter (replaced with mediumConsistency field).
    Improved comments.
    
    ChangeNumberIndexerTest.java:
    Renamed BASE_DN to BASE_DN1.
    Added BASE_DN2 and test emptyDBTwoInitialDSsDifferentDomains().
    In assertExternalChangelogContent(), did some renaming.
    
    SequentialDBCursor.java:
    Improved toString().
    
    ChangeNumberIndexDB.java:
    Removed obsolete FIXME.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@10665 41b1ffd8-f28e-4786-ab96-9950f0a78031
    JnRouvignac
     

15 Apr, 2014

2 commits

  • Small enhancements / cleanups.
    
    
    ChangeNumberIndexer.java:
    Always updated lastAliveCSNs as the very last thing because it is used to decide whether the medium consistency point can move forward.
    
    
    AddMsg.java:
    In toString(), renamed the incorrectly named "changeNumber" attribute to "csn" + merged V1 and V2 protocol paths.
    Extracted method encodeAttributes().
    javadoc cleanup.
    
    DeleteMsg.java, ModifyDNMsg.java, ModifyMsg.java:
    In toString(), renamed the incorrectly named "changeNumber" attribute to "csn" + merged V1 and V2 protocol paths.
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@10662 41b1ffd8-f28e-4786-ab96-9950f0a78031
    JnRouvignac
     
  • git-svn-id: https://svn.forgerock.org/opendj/trunk@10661 41b1ffd8-f28e-4786-ab96-9950f0a78031
    violette
     

14 Apr, 2014

4 commits

  • - Added Scope converter.
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@10658 41b1ffd8-f28e-4786-ab96-9950f0a78031
    violette
     
  • git-svn-id: https://svn.forgerock.org/opendj/trunk@10657 41b1ffd8-f28e-4786-ab96-9950f0a78031
    JnRouvignac
     
  • Code cleanup in ECLServerHandler:
    The eligibleCSN was used when the ECLServerHandler was responsible for inserting replicaDB changes into the changeNumber index DB.
    To this end, the eligibleCSN was computed to provide a kind of "medium consistency point" ("kind of" because it was badly computed).
    After OPENDJ-1174, it is no longer ECLServerHandler's responsibility to inserting replicaDB changes into the changeNumber index DB, so the eligibleCSN is now useless and this commit removes it.
    
    In addition this commit enhances the toString() methods for a better readability.
    
    
    
    ECLServerHandler.java:
    Removed eligibleCSN field + refreshEligibleCSN().
    Renamed computeNextEligibleMessageForDomain() to computeNextAvailableMessage() + simplified code.
    In DomainContext, removed nextNonEligibleMsg field + removed isEligible(), debugInfo() and toString(CSN).
    In dumpState(), made the debug string more readable.
    In buildDomainContexts(), used DomainContext new ctor + extracted method newDomainContext() to build full DomainContext objects in one go + fixed a possible ConcurrentModificationException.
    In DomainContext, made some fields final + added a ctor + made toString() more readable.
    
    ReplicationServerDomain.java:
    Removed getEligibleCSN() and isServerConnected(), now unused.
    
    ReplicationServer.java:
    Removed getEligibleCSN(), now unused.
    
    ReplicationDomainDB.java, JEChangelogDB.java, ChangeNumberIndexer.java:
    Removed getDomainLastAliveCSNs(), now unused.
    
    ExternalChangeLogTest.java
    Consequence of the changes above.
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@10655 41b1ffd8-f28e-4786-ab96-9950f0a78031
    JnRouvignac
     
  • git-svn-id: https://svn.forgerock.org/opendj/trunk@10654 41b1ffd8-f28e-4786-ab96-9950f0a78031
    JnRouvignac
     

11 Apr, 2014

5 commits


10 Apr, 2014

4 commits


08 Apr, 2014

6 commits


07 Apr, 2014

1 commit

  • - Fixed isDN function.
    - LDAPManagementContextFactory.java :removed the unused alwaysSSL var.
    - LDAPConnectionConsoleInteraction.java : 
      -- removed unused parameter canUseSSL.
      -- modified the cannotReadConnectionParameters => more clearer. (thanks to JN)
    N.B This LDAPConnectionConsoleInteraction class will disapear as soon as the SDK will provide the same 'prompt' capabilities.
    (and also because the code is absolutely unmaintainable and redundant.)
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@10632 41b1ffd8-f28e-4786-ab96-9950f0a78031
    violette
     

04 Apr, 2014

4 commits


03 Apr, 2014

2 commits

  • - Moved AuthenticatedConnectionFactory from tools to cli.
      -- Undo modifications on tools about abstract authenticated connection factory. (and deleted the file)
      -- Deleted the file from the tools.
    - Added functions to opendj-cli Utils.
    - Trivial code cleanup.
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@10619 41b1ffd8-f28e-4786-ab96-9950f0a78031
    violette
     
  • JEChangelogDB.java:
    In ChangelogDBPurger.run(), changed code to:
    - support the absence of change number index DB. To simplify matters, code assumes that ds-cfg-compute-change-number does not change during the life time of an RS.
    - purged by using a CSN made up from the purge delay rather than using the previous cookie.
    - sleep 500 millis if there are no changes to purge, or sleep till the next change to purge.
    - gracefully shutdown without fuss in the logs.
    
    
    JEChangeNumberIndexDB.java
    In purgeUpTo(), return the oldest non purged CSN rather than the previous cookie + merged two branches of the code.
    
    ExternalChangeLogTest.java:
    Consequence of the change to JEChangeNumberIndexDB.
    Extracted method assertECLLimits() from ECLCompatTestLimits() + added a loop inside it to let the code persist changes asynchronously from the test thread.
    
    JEChangeNumberIndexDBTest.java:
    Renamed testTrim() to testPurge().
    In newReplicationServer(), enabled ds-cfg-compute-change-number.
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@10617 41b1ffd8-f28e-4786-ab96-9950f0a78031
    JnRouvignac
     

02 Apr, 2014

2 commits

  • git-svn-id: https://svn.forgerock.org/opendj/trunk@10615 41b1ffd8-f28e-4786-ab96-9950f0a78031
    violette
     
  • 
    After OPENDJ-1174, change number index DB is now populated eagerly (was populated lazily).
    This means we can reap the benefits by changing how purging is done for changelogDB.
    Previous purge process was driven by the replicaDBs: first purge replicaDBs then purge the change number index DB and it was causing lots of problems like stale CNIndexDB records for example.
    New purge process is driven by the change number index DB: first purge change number index DB then purge the replicaDBs based on the oldest valid referenced record in the change number index DB.
    
    Moved JEChangeNumberIndexDB purge thread to JEChangelogDB + made it responsible for purging the ChangeNumberIndexDB and all the ReplicaDBs.
    In JEReplicaDB, thread is now only responsible for flushing, previously it was responsible for trimming and flushing which complicated the design and made it less efficient for both operations.
    
    
    
    JEChangelogDB.java:
    Added inner class ChangelogDBPurger.
    Added fields  purgeDelay, cnPurger and latestTrimDate.
    Extracted method startIndexer()
    Removed getChangeNumberIndexDB(boolean) + associated code.
    Reimplemented getDomainLatestTrimDate() and setPurgeDelay().
    
    JEChangeNumberIndexDB.java:
    No longer implements Runnable + removed run().
    Removed fields trimmingThread, trimAge and replicationServer.
    In ctor, removed ReplicationServer parameter.
    Removed startTrimmingThread(), setPurgeDelay() clear(DN, AtomicBoolean).
    Renamed clear(DN) to removeDomain(DN).
    Renamed trim(AtomicBoolean) to purgeUpTo(long).
    Added purgeUpToCookie(ChangeNumberIndexRecord).
    
    JEReplicaDB.java:
    Removed fields latestTrimDate and trimAge.
    In run(), no longer call trim().
    Removed getLatestTrimDate(), isQueueAboveLowMark(), setPurgeDelay() and getQueueSize().
    Renamed trim() to purgeUpTo(CSN).
    Made flush() private + reduced wait time on polling the msgQueue to speed up shutdown.
    Added getNumberRecords() for unit tests.
    
    JEReplicaDBCursor.java:
    Since flushing is now eager, removed all calls to JEReplicaDB.flush().
    Extracted methods closeCursor().
    
    ReplicationServer.java:
    Renamed getTrimAge() to getPurgeDelay() for consistency.
    
    ReplicationDB.java:
    Added getNumberRecords().
    
    ChangeNumberIndexer.java, ChangeNumberIndexerTest.java:
    Removed hacks due to old purging code.
    
    ExternalChangeLogTest.java:
    Called ChangelogDB.setPurgeDelay() instead of ChangeNumberIndexDB.setPurgeDelay(0).
    Consequence of the changes to JEReplicaDB.
    Removed method setPurgeDelayToInitialValue() that was not doing anything (JEChangeNumberIndexDB was always null).
    In getCNIndexDB(), removed useless null check.
    
    JEChangeNumberIndexDBTest.java:
    Removed constants value1, value2, value3 which are invalid cookies.
    Replaced them with fields previousCookie and cookies.
    Added clearCookie() method.
    In addRecord(), removed cookie parameter and build the cookie from the new fields.
    Consequence of the changes to JEChangeNumberIndexDB.
    
    JEReplicaDBTest.java:
    In waitChangesArePersisted(), used JEReplicaDB.getNumberRecords() instead of JEReplicaDB.getQueueSize() + added parameters describing the number of expected records + the counter record window.
    Replaced all calls to JEReplicaDB.flush() with calls to waitChangesArePersisted().
    Consequence of the changes to JEReplicaDB.
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@10614 41b1ffd8-f28e-4786-ab96-9950f0a78031
    JnRouvignac