Why? Do you understand how many problems you bring with this approach? --Yakov
2015-07-14 18:00 GMT+03:00 Dmitriy Setrakyan <[email protected]>: > Yakov, > > We cannot start a client inside of an agent simply because agent will be > started outside of the cluster where grid is deployed. Agent will be > connecting to the grid using HTTP Rest requests. > > D. > > On Tue, Jul 14, 2015 at 6:16 AM, Yakov Zhdanov <[email protected]> > wrote: > > > I like the design where agent is a plugin to Ignite. Agent-ControlCenter > > can be incorporated into the singleton cluster-wide service deployed by > > plugin on start. This approach seems very good and clean to me: > > 1. Easy to config - just drop JAR with plugin to classpath > > 2. It is native to the cluster - it operates inside. > > 3. Failover works out of the box. > > > > Thanks! > > > > --Yakov > > > > 2015-07-02 19:35 GMT+03:00 Dmitriy Setrakyan <[email protected]>: > > > > > On Thu, Jul 2, 2015 at 8:08 AM, Sergey Evdokimov < > > [email protected]> > > > wrote: > > > > > > > Yes, Web Agent can open connection to Control Center at any time. Web > > > Agent > > > > is started up as much as started up cluster, but user looks to > Control > > > > Center infrequently. Web Agent have to keep connection always opened > or > > > we > > > > need a way to notify Web Agent about new web-session on Web Control > > > Center. > > > > > > > > > > Sergey, the agent should automatically reconnect whenever a connection > is > > > lost. For example, it can send a keep-alive ping every 2 seconds back > to > > > the web control center. > > > > > > If you having doubts in the approach, please ping me on Skype so we > could > > > flush out the details. > > > > > > > > > > > > > > On Thu, Jul 2, 2015 at 5:53 PM, Dmitriy Setrakyan < > > [email protected] > > > > > > > > wrote: > > > > > > > > > On Thu, Jul 2, 2015 at 7:29 AM, Sergey Evdokimov < > > > > [email protected]> > > > > > wrote: > > > > > > > > > > > Web Agent can be shipped as Ignite plugin and start inside the > > > cluster > > > > as > > > > > > service to avoid unnecessary configuration. > > > > > > > > > > > > How Web Agent will detect that Web Control Center need a data? > Web > > > > > Control > > > > > > Center cannot open connection to cluster, because cluster may be > in > > > > local > > > > > > network without static IP. Do you mean that Web Agent will keep > > > opened > > > > > > connection to Web Control Center always? > > > > > > > > > > > > > > > > However, the Ignite web agent should be able to open a connection > to > > > the > > > > > web control center, no? > > > > > > > > > > > > > > > > > > > > > > On Thu, Jul 2, 2015 at 5:12 PM, Alexey Kuznetsov < > > > > > [email protected]> > > > > > > wrote: > > > > > > > > > > > > > Igniters, > > > > > > > > > > > > > > I'm working on Web Control Center and first release is near. > > > > > > > In first release we will provide UI for cluster and caches > > > > > configuration. > > > > > > > > > > > > > > In next releases we will provide Monitoring, SQL and Schema > > Import > > > > > > Utility. > > > > > > > But those advanced features require access to Ignite cluster > (for > > > > > > > Monitoring and SQL) > > > > > > > and access to DB server for Schema Import. > > > > > > > > > > > > > > After some thoughts we decided to create a so-called "web > agent" > > it > > > > > will > > > > > > be > > > > > > > started "near" cluster and DB will connect to it and send all > > > needed > > > > > info > > > > > > > to Web Control Center. > > > > > > > > > > > > > > Any ideas, thoughts and suggestions are very welcome. > > > > > > > > > > > > > > Thanks. > > > > > > > > > > > > > > -- > > > > > > > Alexey Kuznetsov > > > > > > > GridGain Systems > > > > > > > www.gridgain.com > > > > > > > > > > > > > > > > > > > > > > > > > > > >
