Unify standalone and distributed configurations #1864

Closed
lvca opened this Issue Dec 4, 2013 · 0 comments

Projects

None yet

1 participant

@lvca
Member
lvca commented Dec 4, 2013

From the beginning we supported 2 different environments: classic and distributed. For this reason we've:

  • orientdb-server-config.xml -> standalone server
  • orientdb-dserver-config.xml -> distributed server

and

  • server.sh and .bat -> standalone server
  • dserver.sh and .bat -> distributed server

and we miss dshutdown.sh and .bat that uses the distributed settings to shutdown the node. So I'm thinking to a more elegant solution having just 1 file for both and use settings to enable/disable the distributed plugin:

server.sh -Ddistributed=true

and put this in configuration like:

    <handler class="com.orientechnologies.orient.server.hazelcast.OHazelcastPlugin">
        <parameters>
            <parameter name="enabled" value="${distributed}" />

This should already work and let us to keep only ONE configuration file for both scenarios, even with shutdown.

@lvca lvca was assigned Dec 4, 2013
@lvca lvca added the high priority label Aug 28, 2014
@lvca lvca modified the milestone: 2.0-M1, 2.0-M2 Sep 17, 2014
@lvca lvca added the In Progress label Sep 29, 2014
@lvca lvca added a commit that referenced this issue Sep 29, 2014
@lvca lvca Fixed issue #1864
Unify standalone and distributed configurations
07231d2
@lvca lvca removed the In Progress label Sep 29, 2014
@lvca lvca closed this Sep 29, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment