[Design of Messaging on JBoss (Messaging/JBoss)] - Annoyance when running unit tests in eclipse
by timfox
Both Clebert and I are getting
| log4j error: setFile(null,true) call failed.
| java.io.FileNotFoundException: /logs/messaging-.log (No such file or directory)
| at java.io.FileOutputStream.openAppend(Native Method)
| at java.io.FileOutputStream.<init>(FileOutputStream.java:177)
| at java.io.FileOutputStream.<init>(FileOutputStream.java:102)
| at org.apache.log4j.FileAppender.setFile(FileAppender.java:289)
| at org.apache.log4j.FileAppender.activateOptions(FileAppender.java:163)
| at org.apache.log4j.DailyRollingFileAppender.activateOptions(DailyRollingFileAppender.java:215)
| at org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:256)
| at org.apache.log4j.xml.DOMConfigurator.parseAppender(DOMConfigurator.java:220)
| at org.apache.log4j.xml.DOMConfigurator.findAppenderByName(DOMConfigurator.java:150)
| at org.apache.log4j.xml.DOMConfigurator.findAppenderByReference(DOMConfigurator.java:163)
| at org.apache.log4j.xml.DOMConfigurator.parseChildrenOfLoggerElement(DOMConfigurator.java:425)
| at org.apache.log4j.xml.DOMConfigurator.parseRoot(DOMConfigurator.java:394)
| at org.apache.log4j.xm
|
When running unit tests in eclipse.
Clebert suggests this is due to some change made by Andy recently in log4j.xml.
Any ideas?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177351#4177351
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177351
17 years, 6 months
[Design of JBossCache] - Re: memcached client/server
by bela@jboss.com
Yes, ExpirationPolicy would certainly be needed, compared to defining a policy for an entire region.
Regarding consisten hashing: the Data Partitioning feature calls for metadata, replicated to all JBC instances, which keeps track of allocation of stripes to instances.
However, as an alternative, as you mentioned, we could use consistent hashing, to define where data is placed in the cluster. This could also be used to derive the primary node and backup nodes for a given stripe, instead of using metadata.
Interesting comparison: Google File System (GFS) uses metedata, but it is maintained by a single central server. However, this is not an issue as it can be reconstructed by consulting the cluster nodes.
We have to think a bit more about whether to use consistent hashing, or metadata, to place data across a cluster. I suspect metadata gives us more flexibility in supporting more exotic setups. If we store local metadata in every node, then we don't have to replicate metadata across the cluster, but the (JGroups) coordinator could maintain it. When it goes down, the next-in-line takes over, soliciting metadata from all nodes...
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177298#4177298
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177298
17 years, 6 months
[Design of JBossCache] - Re: memcached client/server
by genman
There's probably some value in having a Memcached-talking CacheLoader as well, and fairly trivial to write. It might be good for testing the server, at least.
One interesting thing that memcached does is allow for the specification of an eviction time per key. As a emulating server, I suppose that my ExpirationPolicy might come into play.
Not sure consistent hashing really fits in with the Data Partitioning design since it seems to concern itself with load/data balancing and reliability.
But I sense that data balancing is possible with consistent hashing. For instance, when a node joins or leaves, each existing instance would examine their tree and "move" any data rehashed for the new/existing member to that instance. And some measure of reliability certainly is possible with consistent hashing: Hash an Fqn to two nodes and store two copies.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177289#4177289
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177289
17 years, 6 months