在Windows和Linux之间定位数据库复制

时间:2016-08-09 13:30:35

标签: linux windows replication orientdb

是否可以在Linux和Windows之间复制OrientDB数据库?

我正在使用Orient DB 2.1.11。我按照以下说明设置了复制:http://orientdb.com/docs/2.0/orientdb.wiki/Tutorial-Setup-a-distributed-database.html。复制在两个本地Windows数据库实例之间工作,但如果我尝试使用原始 default-distributed-db-config.json 设置将Linux数据库实例复制到Windows,则会收到以下错误: Windows方面:

  

解压缩文件luceneIndexes / TABLE_NAME.INDEX_NAME / write.lock ...   复制数据库时出现OHazelcastPlugin] {db = DB_NAME} [Slave]错误   ' DB_NAME'在本地服务器上

即使分布式db config json文件中的autoDeploy为false,我也会在复制之前手动复制数据库。

顺便说一句:在Linux上,此警告出现在错误之前:

  

2016-08-09 15:16:33:873 WARNI [Jenkins]添加了新节点id = Member   [192.168.10.98]:2434 name = ext:b04653c1-6b97-4be3-9acc-1316f6757706   [OHazelcastPlugin] [192.168.10.73]:2434 [TestReplica] [3.5.3]虽然   wait finalize join calls ... java.util.concurrent.TimeoutException:   呼叫调用{serviceName =' hz:core:clusterService',   OP = FinalizeJoinOperation {postJoinOp = PostJoinOperation {操作= [{com.hazelcast.spi.impl.eventservice.impl.operations.PostJoinRegistrationOperation =服务名'空&#39 ;,   partitionId = -1,callId = 0,invocationTime = -1,waitTimeout = -1,   callTimeout = 9223372036854775807}   com.hazelcast.spi.impl.proxyservice.impl.operations.PostJoinProxyOperation {服务名='空&#39 ;,   partitionId = -1,callId = 0,invocationTime = -1,waitTimeout = -1,   callTimeout = 9223372036854775807}   com.hazelcast.map.impl.operation.PostJoinMapOperation {服务名='空&#39 ;,   partitionId = -1,callId = 0,invocationTime = -1,waitTimeout = -1,   callTimeout = 9223372036854775807}]}} MemberInfoUpdateOperation {   的MemberInfo {地址=地址[192.168.10.73]:2434}   MemberInfo {address = Address [192.168.10.98]:2434}},partitionId = -1,   replicaIndex = 0,tryCount = 100,tryPauseMillis = 500,invokeCount = 1,   callTimeout = 60000,target = Address [192.168.10.98]:2434,   backupsExpected = 0,backupsCompleted = 0}遇到超时   com.hazelcast.spi.impl.operationservice.impl.InvocationFuture.resolveApplicationResponse(InvocationFuture.java:366)     在   com.hazelcast.spi.impl.operationservice.impl.InvocationFuture.resolveApplicationResponseOrThrowException(InvocationFuture.java:334)     在   com.hazelcast.spi.impl.operationservice.impl.InvocationFuture.get(InvocationFuture.java:225)     在   com.hazelcast.util.FutureUtil.executeWithDeadline(FutureUtil.java:294)     在   com.hazelcast.util.FutureUtil.waitWithDeadline(FutureUtil.java:278)     在   com.hazelcast.util.FutureUtil.waitWithDeadline(FutureUtil.java:252)     在   com.hazelcast.cluster.impl.ClusterServiceImpl.startJoin(ClusterServiceImpl.java:1024)     在   com.hazelcast.cluster.impl.ClusterServiceImpl.handleJoinRequest(ClusterServiceImpl.java:706)     在   com.hazelcast.cluster.impl.operations.JoinRequestOperation.run(JoinRequestOperation.java:40)     在   com.hazelcast.spi.impl.operationservice.impl.OperationRunnerImpl.run(OperationRunnerImpl.java:137)     在   com.hazelcast.spi.impl.operationservice.impl.OperationRunnerImpl.run(OperationRunnerImpl.java:315)     在   com.hazelcast.spi.impl.operationexecutor.classic.OperationThread.processPacket(OperationThread.java:142)     在   com.hazelcast.spi.impl.operationexecutor.classic.OperationThread.process(OperationThread.java:115)     在   com.hazelcast.spi.impl.operationexecutor.classic.OperationThread.doRun(OperationThread.java:101)     在   com.hazelcast.spi.impl.operationexecutor.classic.OperationThread.run(OperationThread.java:76)

0 个答案:

没有答案