[OAK-3417] oak-run OakFixture might set incorrect clusterIDs

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.0.21, 1.2.6, 1.3.7
• Fix Version/s: 1.0.22, 1.2.7, 1.3.8, 1.4
• Component/s: run
• Assignee: Julian Reschke
• Reporter: Julian Reschke
• Created: 17/Sep/15 14:45
• Updated: 02/Mar/16 14:29
• Resolved: 28/Sep/15 14:01

Description

Seen in OakFixture.java:

            @Override
            public Oak[] setUpCluster(int n) throws Exception {
                Oak[] cluster = new Oak[n];
                kernels = new DocumentMK[cluster.length];
                for (int i = 0; i < cluster.length; i++) {
                    MongoConnection mongo = new MongoConnection(uri);
                    DocumentMK.Builder mkBuilder = new DocumentMK.Builder().
                            setMongoDB(mongo.getDB()).
                            memoryCacheSize(cacheSize).
                            setPersistentCache("target/persistentCache,time").
                            setClusterId(i).
                            setLogging(false);
                    setupBlobStore(mkBuilder);
                    kernels[i] = mkBuilder.open();
                    cluster[i] = newOak(kernels[i].getNodeStore());
                }
                return cluster;
            }

...however, setClusterId(0) is special (it generates it automatically}