OK - in the meantime I re-added and then started in sinlge node mode and we
get success as such:
ubuntu@orientdb04:/opt/orientdb/orientdb-community-1.7.7/bin$ ./server.sh
.
.` `
, `:.
`,` ,:`
.,. :,,
.,, ,,,
. .,.::::: ```` :::::::::
:::::::::
,` .::,,,,::.,,,,,,`;; .: :::::::::: :::
:::
`,. ::,,,,,,,:.,,.` ` .: ::: ::: :::
:::
,,:,:,,,,,,,,::. ` ` `` .: ::: ::: :::
:::
,,:.,,,,,,,,,: `::, ,, ::,::` : :,::` :::: ::: ::: :::
:::
,:,,,,,,,,,,::,: ,, :. : :: : .: ::: :::
:::::::
:,,,,,,,,,,:,:: ,, : : : : .: ::: :::
:::::::::
` :,,,,,,,,,,:,::, ,, .:::::::: : : .: ::: ::: :::
:::
`,...,,:,,,,,,,,,: .:,. ,, ,, : : .: ::: ::: :::
:::
.,,,,::,,,,,,,: `: , ,, : ` : : .: ::: ::: :::
:::
...,::,,,,::.. `: .,, :, : : : .: ::::::::::: :::
:::
,::::,,,. `: ,, ::::: : : .: :::::::::
::::::::::
,,:` `,,.
,,, .,`
,,. `, GRAPH DATABASE
`` `.
``
www.orientdb.org
`
2014-08-12 11:42:55:082 INFO Loading configuration from:
/opt/orientdb/orientdb-community-1.7.7/config/orientdb-server-config.xml...
[OServerConfigurationLoaderXml]
2014-08-12 11:42:55:727 INFO OrientDB Server v1.7.7 (build UNKNOWN@r;
2014-07-10 22:04:36+0200) is starting up... [OServer]
2014-08-12 11:42:55:739 INFO Databases directory:
/opt/orientdb/orientdb-community-1.7.7/databases [OServer]
2014-08-12 11:42:55:875 INFO Listening binary connections on 0.0.0.0:2424
(protocol v.21, socket=default) [OServerNetworkListener]
2014-08-12 11:42:55:880 INFO Listening http connections on 0.0.0.0:2480
(protocol v.10, socket=default) [OServerNetworkListener]
2014-08-12 11:42:55:907 INFO Installing dynamic plugin
'studio-1.7.5.zip'... [OServerPluginManager]
2014-08-12 11:42:56:116 INFO Installing GREMLIN language v.2.5.0 -
graph.pool.max=50 [OGraphServerHandler]
2014-08-12 11:42:56:131 INFO Installing Script interpreter. WARN:
authenticated clients can execute any kind of code into the server by using
the following allowed languages: [sql] [OServerSideScriptInterpreter]
2014-08-12 11:42:56:131 INFO OrientDB Server v1.7.7 is active. [OServer]
2014-08-12 11:43:53:750 WARN segment file 'database.ocf' was not closed
correctly last time [OSingleFileSegment]
2014-08-12 11:43:54:053 WARN Storage GeoLocation was not closed properly.
Will try to restore from write ahead log. [OLocalPaginatedStorage]
2014-08-12 11:43:54:053 INFO Looking for last checkpoint...
[OLocalPaginatedStorage]
2014-08-12 11:43:54:062 INFO FULL checkpoint found. [OLocalPaginatedStorage]
2014-08-12 11:43:54:064 INFO Data restore procedure from full checkpoint is
started. Restore is performed from LSN OLogSequenceNumber{segment=572,
position=36527107} [OLocalPaginatedStorage]
2014-08-12 11:43:54:929 INFO Apply last batch of operations are read from
WAL. [OLocalPaginatedStorage]
2014-08-12 11:43:54:929 WARN Record
com.orientechnologies.orient.core.storage.impl.local.paginated.wal.OCheckpointEndRecord{lsn=OLogSequenceNumber{segment=572,
position=36527131}} will be skipped during data restore.
[OLocalPaginatedStorage]
2014-08-12 11:43:55:332 INFO Storage data restore was completed
[OLocalPaginatedStorage]
2014-08-12 11:43:56:019 INFO Wait till indexes restore after crash was
finished. [OIndexManagerShared]
2014-08-12 11:43:56:114 INFO Start creation of index
AbstractLocation.locationId [OIndexManagerShared$RecreateIndexesTask]
2014-08-12 11:43:56:302 INFO Index AbstractLocation.locationId was
successfully created and rebuild is going to be started.
[OIndexManagerShared$RecreateIndexesTask]
2014-08-12 11:43:56:313 INFO - Rebuilding index
GeoLocation.AbstractLocation.locationId (estimated 602207 items)...
[OIndexRebuildOutputListener]
On Tuesday, August 12, 2014 12:39:34 PM UTC+1, Lvc@ wrote:
>
> If you manually deploy the database (suggested if it's quite big), assure
> to have:
>
> "autoDeploy":false,
> "hotAlignment":true,
>
> In $ORIENTDB_HOME/config/distributed-config.json file.
>
> This avoid the auto deploy and activate the hotAlignment.
>
> Lvc@
>
>
> On 12 August 2014 13:36, Shaun Barker <[email protected] <javascript:>>
> wrote:
>
>> ubuntu@orientdb04:/opt/orientdb/orientdb-community-1.7.7/bin$ ll
>> ../databases/
>> total 20
>> drwxr-xr-x 5 ubuntu ubuntu 4096 Aug 12 11:22 ./
>> drwxr-xr-x 10 ubuntu ubuntu 4096 Aug 12 10:45 ../
>> drwxr-xr-x 2 ubuntu ubuntu 4096 Aug 12 11:22 GeoLocation/
>> drwxr-xr-x 2 ubuntu ubuntu 4096 Aug 12 11:22 GratefulDeadConcerts/
>> drwxr-xr-x 2 ubuntu ubuntu 4096 Aug 12 11:10 testy/
>> ubuntu@orientdb04:/opt/orientdb/orientdb-community-1.7.7/bin$ ll
>> ../databases/GeoLocation/
>> total 12
>> drwxr-xr-x 2 ubuntu ubuntu 4096 Aug 12 11:22 ./
>> drwxr-xr-x 5 ubuntu ubuntu 4096 Aug 12 11:22 ../
>> -rw-r--r-- 1 ubuntu ubuntu 333 Aug 12 11:22 distributed-config.json
>> ubuntu@orientdb04:/opt/orientdb/orientdb-community-1.7.7/bin$
>>
>> On Monday, August 11, 2014 5:35:22 PM UTC+1, Shaun Barker wrote:
>>
>>> Hi
>>>
>>> We are running orientdb-community-1.7.5. We have an initial db
>>> (generated from some data extraction in a dev sandbox) that needs to be
>>> loaded into our orientdb node cluster of 4 nodes set up in distributed set
>>> up. We are running out of box in distributed mode with the only change
>>> being that the nodes have tweaked hazelcast to turn off broadcast and
>>> discover only specified nodes by ip address.
>>>
>>> Due to IP connectivity issues we established the easiest way was to add
>>> the initial 'seed-database' to one node from the cluster (stop server, copy
>>> to database folder, start server) and let it re-distribute the database to
>>> the other nodes.
>>>
>>> The seed database is 3Gb in size.
>>>
>>> What actually happens is the node that has the data does not start at
>>> all - it gets stuck in a 'STARTING' state. The other nodes in the cluster
>>> (when they are all re-started) also do not start.
>>>
>>> In order to investigate I tried out some other angles. I established
>>> that if one node was taken out of the cluster, and re-started in non
>>> distributed mode it would eventually start and would re-index the database
>>> resulting in about an hours worth of wait. If this node was then
>>> re-introduced to the cluster the cluster fails again. If I repeated the
>>> steps on each node (take out of cluster, run standalone, copy db in,
>>> restart) then each node will re-index the data. However upon bringing all
>>> nodes back to the cluster each with the exact same copy of the database
>>> indexed then the cluster will not run properly again. If I make no other
>>> changes that to remove the db sufolder then all works again.
>>>
>>> So my question is this: what is the correct and supported way to 'seed a
>>> database' into a cluster. Are there any size limitations? Indeed is there
>>> some config tweak needed?
>>>
>>> thanks
>>>
>>> Shaun
>>>
>>>
>>>
>>>
>>>
>>> --
>>
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "OrientDB" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected] <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
--
---
You received this message because you are subscribed to the Google Groups
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
