You're right, there's no way to do it from the manager. But there's the
"Alchemi Console" which will let you connect to a manager and view the info.
Alchemi.Core.Console? or something like that.
In-memory storage was a very new idea when I joined the project. I don't
think I added it, but I might have; actually, I think Tibor did. Long time
ago. Originally it was just SQL Server, and... SQL Server. I think that
was back before MS gave away the Express version for free. I actually think
that was the biggest motivator for supporting different data storage
methods: not everyone had licenses for SQL Server. So it makes sense it
would default to that, just for legacy reasons.
One of the general ideas I was trying to push was to make it as painless as
possible to get the grid set up. You're struggling with things that I
genuinely don't think you should be. Ultimately, with some of the p2p and
election algorithm ideas, my goal was that you could install Alchemi on any
machine and it would just auto-discover other Alchemi nodes on the network.
You wouldn't have to even specify whether you're running a client or server
(er, Executor or Manager) because every node would be capable of serving
both purposes. You just submitted a job/GApplication to your local PC, and
any redirection of work would be handled transparently. Additionally, the
whole grid would be fault tolerant, so if any node went down, a new manager
(or managers) would be "elected" to take over, and all of the bookkeeping
would be synchronized between the nodes. When it came back up, or if the
network segmentation disappeared, the bookkeeping info would again be
synchronized. In this case, it would err on the side of executing a GThread
multiple times rather than not at all.
Honestly, I've built half of this stuff already. The sync algorithms have
been written and the election algorithms have been implemented. They just
never made it into Alchemi.
Again, so much of this needs to be revisited, but realistically it'll
probably be another 3-6 weeks -- or more -- before I can really jump back
into it.
-- Jonathan
On Wed, Apr 6, 2011 at 8:12 AM, Richard Foreman <[email protected]>wrote:
> I finally got the executors connecting to the manager in the source code,
> the biggest obstacle is the fact that the manager defaults to sql server for
> storage, which would be fine if it would drop back to in memory storage
> instead of just failing (I just pointed it to in memory storage right where
> it returned form reading the configuration file). I had to make a few minor
> changes to get it working, but nothing major. I havent fully tested it yet
> because Ive been swamped with work, but hopefully that will mellow out soon.
>
> Am I just blind or is there no way to actually view the status of the
> users, threads, and apps directly from the manager?
>
>
> ------------------------------------------------------------------------------
> Xperia(TM) PLAY
> It's a major breakthrough. An authentic gaming
> smartphone on the nation's most reliable network.
> And it wants your games.
> http://p.sf.net/sfu/verizon-sfdev
> _______________________________________________
> alchemi-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/alchemi-users
>
>
------------------------------------------------------------------------------
Xperia(TM) PLAY
It's a major breakthrough. An authentic gaming
smartphone on the nation's most reliable network.
And it wants your games.
http://p.sf.net/sfu/verizon-sfdev
_______________________________________________
alchemi-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/alchemi-users
