Hi,

I've been reading from the following places:
https://karaf.apache.org/manual/cellar/latest-4/
http://blog.nanthrax.net/2015/09/whats-new-in-apache-karaf-cellar-4-0-0/

I'm trying to make a 3 node cluster, 2 of the nodes (node1 and node2) having
the webconsole feature installed locally and the other (node3) proxying to
those nodes, this is what I did:

The steps I followed for node1 and node2 are the same (except for the
install of cellar-http-balancer, done only on node1):
karaf@node1()> feature:install http
karaf@node1()> feature:install http-whiteboard
karaf@node1()> feature:repo-add cellar
karaf@node1()> feature:install cellar
karaf@node1()> cluster:feature-install default cellar-http-balancer (only
node1)
karaf@node1()> feature:install webconsole

The steps I followed for node3:
karaf@node3()> feature:install http
karaf@node3()> feature:install http-whiteboard
karaf@node3()> feature:repo-add cellar
karaf@node3()> feature:install cellar

In node3 I got an error when registering node2's webconsole (node1 was
registered first):
org.osgi.service.http.NamespaceException: alias: '/system/console' is
already in use in this or another context

In node3:
karaf@node3()> cluster:http-list default
Alias               | Locations
------------------------------------------------------------------------------------------------------
/features           | http://192.168.1.56:8181/features
http://192.168.1.52:8181/features
/system/console     | http://192.168.1.56:8181/system/console
http://192.168.1.52:8181/system/console
/gogo               | http://192.168.1.56:8181/gogo
http://192.168.1.52:8181/gogo
/system/console/res | http://192.168.1.56:8181/system/console/res
/instance           | http://192.168.1.56:8181/instance
http://192.168.1.51:8181/instance

karaf@node3()> http:list
ID  | Servlet                    | Servlet-Name    | State       | Alias        
      
| Url
----------------------------------------------------------------------------------------------------------------
105 | FeaturesPlugin             | ServletModel-20 | Failed      | /features    
      
| [/features/*]
103 | CellarBalancerProxyServlet | ServletModel-10 | Failed      |
/system/console     | [/system/console/*]
104 | KarafOsgiManager           | ServletModel-16 | Failed      |
/system/console     | [/system/console/*]
103 | CellarBalancerProxyServlet | ServletModel-3  | Deployed    |
/system/console     | [/system/console/*]
103 | CellarBalancerProxyServlet | ServletModel-2  | Undeployed  | /features    
      
| [/features/*]
108 | InstancePlugin             | ServletModel-18 | Deployed    | /instance    
      
| [/instance/*]
103 | CellarBalancerProxyServlet | ServletModel-7  | Failed      | /gogo        
      
| [/gogo/*]
103 | CellarBalancerProxyServlet | ServletModel-12 | Deployed    | /gogo        
      
| [/gogo/*]
103 | CellarBalancerProxyServlet | ServletModel-6  | Undeployed  | /instance    
      
| [/instance/*]
103 | CellarBalancerProxyServlet | ServletModel-11 | Deployed    | /features    
      
| [/features/*]
103 | CellarBalancerProxyServlet | ServletModel-5  | Deployed    |
/system/console/res | [/system/console/res/*]
103 | CellarBalancerProxyServlet | ServletModel-9  | Failed      | /features    
      
| [/features/*]
104 | KarafOsgiManager           | ServletModel-14 | Failed      |
/system/console     | [/system/console/*]
106 | GogoPlugin                 | ServletModel-22 | Failed      | /gogo        
      
| [/gogo/*]
103 | CellarBalancerProxyServlet | ServletModel-4  | Undeployed  | /gogo        
      
| [/gogo/*]
103 | CellarBalancerProxyServlet | ServletModel-8  | Failed      | /instance    
      
| [/instance/*]


So, if I go to:
node3:8181/system/console
And node1 is up it works correctly, if I stop node1 It fails because node2's
stuff was not registered


What do I need to do so there is no conflict registering the features from
node2?

Thanks










--
View this message in context: 
http://karaf.922171.n3.nabble.com/Cellar-Load-balancer-setup-tp4049717.html
Sent from the Karaf - User mailing list archive at Nabble.com.

Reply via email to