Phil 7.18.17

7:00 – 8:00 Research

  • Feeling blue and it’s hard to focus.
  • More C&C
    • We would have, on the one hand, a mimetic sociability, and, on the other, a cathartic sociability. But once more this is an antimony that depends upon circumstances and upon human nature. If we mention here both lines of thinking it is not in order to plead for one rather than the other, but to put both in perspective. [p 92]
    • Ratio decidendi [p 95]
    • At the same time, the more precise the information, the less the field is left free for differences and individual positions. Gradually these are supplanted by collective positions in the consciousness of group members. If the members continue for long enough, the consensus approximates to these values, just as a house under construction does to the architect’s plan. [p 97]
      • I think that I see this as a dimension reduction issue. Too many dimensions, and the distances are too great to come to a consensus, average or extreme. But some dimensions have very little variability, and can be discarded. Some dimensions can be placed outside of the scope of the discussion while others are included by mutual consent. The process of interactive dimension reduction continues until there is enough range of opinion across a sufficiently small set of dimensions that it is possible for a group opinion to emerge. The qualities would be different for different groups – humans, AI, or genes.
  • Chat with Stacy on messenger this morning:
  • Phil, this made me think of your comment about how robots may be changing humans for the worse:
    Opinion | The Trouble With Sex Robots
    Sexual consent is a serious enough problem without bots encouraging men to think it’s unnecessary.
    Thanks – I downloaded and scanned the source paper. I think my basic concern is that ‘power corrupts’, and the moment our machines afford a power dynamic similar to a human one, there are many opportunities for things to go badly.
    7:40AMInteresting. Can a toaster afford a power dynamic (“Make my toast!”)? What about a life-size blow-up female doll? What about a male real doll?
    I think it’s in the eye of the beholder. I have ‘relationships’ with some of my bicycles that are strong enough that I can’t sell them. But an old phone, arguably something that I spend more time with, I can dispose of easily.
    With respect to the toaster, I think there is a continuum? Imagine at one end, a purely mechanical toaster. Push lever, pause, toast pops up.
    On the other end is a human butler, who you ask to make toast. Machines are now traversing that range. It wouldn’t be hard, for example to have Alexa interact with an IoT toaster to make toast on request.
    And Alexa is designed for you to be curt with it.
    I think I heard on NPR that there are researchers looking into how our interactions with voice-activated technology will impact our interactions with human beings, since the same affordance (speech) is being used on entities place in different power dynamics.
    Pulling this around to my research (Because why wouldn’t you?), these sorts of novel inputs may affect how we flock and move through belief space.

9:00 – 5:30 – BRI

  • Generating the message from GeocoderService, but GeoIngestService fails.
  • Going back to my geomesa-tutorials. That fails too: Exception in thread “main” java.util.concurrent.ExecutionException: org.apache.hadoop.ipc.RemoteException( File /hbase/.tmp/data/default/geomesa4/d7c3215c807b2ad9bb32555efbec133a/.regioninfo could only be replicated to 0 nodes instead of minReplication (=1). There are 1 datanode(s) running and no node(s) are excluded in this operation.
    • It’s possible the node is full. Trying that first
    • Stopping everything and reformatted.
    • Can’t even copy in the GeoMesa jar:
      ~/hadoop-2.7.3$ bin/hadoop fs -put ${GEOMESA_HOME}dist/hbase/geomesa-hbase-distributed-runtime_2.11-1.3.2-SNAPSHOT.jar hdfs://localhost:9000/hbase/lib/
      Picked up JAVA_TOOL_OPTIONS: -Dgeomesa.hbase.coprocessor.path=hdfs://localhost:9000/hbase/lib/geomesa-hbase-distributed-runtime_2.11-1.3.2-SNAPSHOT.jar
      17/07/18 10:55:05 WARN hdfs.DFSClient: DataStreamer Exception
      org.apache.hadoop.ipc.RemoteException( File /hbase/lib/geomesa-hbase-distributed-runtime_2.11-1.3.2-SNAPSHOT.jar._COPYING_ could only be replicated to 0 nodes instead of minReplication (=1).  There are 0 datanode(s) running and no node(s) are excluded in this operation.
      	at org.apache.hadoop.hdfs.server.blockmanagement.BlockManager.chooseTarget4NewBlock(
      	at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getNewBlockTargets(
      	at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getAdditionalBlock(
      	at org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.addBlock(
      	at org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.addBlock(
      	at org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(
      	at org.apache.hadoop.ipc.ProtobufRpcEngine$Server$
      	at org.apache.hadoop.ipc.RPC$
      	at org.apache.hadoop.ipc.Server$Handler$
      	at org.apache.hadoop.ipc.Server$Handler$
      	at Method)
      	at org.apache.hadoop.ipc.Server$
      	at org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(
      	at com.sun.proxy.$Proxy10.addBlock(Unknown Source)
      	at org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolTranslatorPB.addBlock(
      	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      	at sun.reflect.NativeMethodAccessorImpl.invoke(
      	at sun.reflect.DelegatingMethodAccessorImpl.invoke(
      	at java.lang.reflect.Method.invoke(
      	at com.sun.proxy.$Proxy11.addBlock(Unknown Source)
      	at org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.locateFollowingBlock(
      	at org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.nextBlockOutputStream(
      	at org.apache.hadoop.hdfs.DFSOutputStream$
      put: File /hbase/lib/geomesa-hbase-distributed-runtime_2.11-1.3.2-SNAPSHOT.jar._COPYING_ could only be replicated to 0 nodes instead of minReplication (=1).  There are 0 datanode(s) running and no node(s) are excluded in this operation.
    • Looks like the problem was that you should not format the dfs multiple times. Hadoop gets out of sync. Deleted the /tmp/hadoop-pfeldman directory and files, then reformatted and restarted. That appears to be working.