distributed

I'm looking for a simple clock synchronization protocol that would be easy to implement with small footprint and that would work also in the absence of internet connection, so that it could be used e.g. within closed laboratory networks. To be clear, I'm not looking for something that can be used just to order events (like vector clocks), but something that would enable processes on different nodes to synchronize their actions based on local clocks. As far as I understand, this would require a solution that can take clock drift into account. Presence of TCP/IP or similar relatively low-latency

Simple script below is launched with args shown in it's header. It behaves differently, but often one of the workers hangs and prints these "CreateSession still waiting for some other task" messages. Why does a new MonitoredTrainingSession need others? And why don't the others wait for it to start? # #!/bin/bash # python train.py --job master --task 0 & # python train.py --job worker --task 0 & # python train.py --job worker --task 1 & # python train.py --job worker --task 2 & import argparse import tensorflow as tf parser = argparse.ArgumentParser() parser.add_argument('--job', type=str)

I configured hadoop using kerberos, everything works fine, I can browse hdfs, submit jobs, etc. But failed http web authentication. I use hadoop-0.20.2 in cdh3u2, which supports HTTP SPNEGO. HTTP authentication related configurations in core-site.xml are as follows: <!-- HTTP web-consoles Authentication --> <property> <name>hadoop.http.filter.initializers</name> <value>org.apache.hadoop.security.AuthenticationFilterInitializer</value> </property> <property> <name>hadoop.http.authentication.type</name> <value>kerberos</value> </property> <property> <name>hadoop.http.authentication.token

after some research, we opted for working with Drupal on our next project and we are a distributed team. Since Drupal stores (based on what we saw until now) all it's content on a database, how can we, as a distributed team work together on this project? What are the best practices we should take? We thought about using a shared database server for this task, but it whould simply destroy the performance we should need to get this project going. Any suggestions about that? Jeremy's answer (+1) is already quite comprehensive. Some additional more practical-oriented advice follows in no

I've been using RMI for a project I am currently working on and I want to bind from multiple hosts to a single RMI registry. However when I attempt to do so I get an error saying java.rmi.AccessException: Registry.Registry.bind disallowed; origin / 192.168.0.9 is non-local host I did so googling and it seems that RMI stops remote hosts from binding by default, what I want to know is there some way of overriding or bypassing this? If anyone any suggestions on how to get past this issue they would be highly appreciated, i've tried using different policy files and overriding the security manger

When using distributed and scalable architecture, eventual consistency is often a requirement. Graphically, how to deal with this eventual consistency? Users are used to click save, and see the result instantaneously... with eventual consistency it's not possible. How to deal with the GUI for such scenarios? Please note the question applies both for desktop applications and web applications. PS: I'm working with the Microsoft platform, but I imagine the question applies to any technology... A Task Based UI fits this model great. You create and execute tasks from the UI. You can also have