You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@asterixdb.apache.org by "Ian Maxon (JIRA)" <ji...@apache.org> on 2015/09/14 19:43:47 UTC

[jira] [Closed] (ASTERIXDB-1082) Managix issues encountered when creating a single node instance of AsterixDB on AWS

     [ https://issues.apache.org/jira/browse/ASTERIXDB-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ian Maxon closed ASTERIXDB-1082.
--------------------------------
    Resolution: Later
      Assignee: Ian Maxon

The NPE will be fixed in ASTERIXDB-1089, but some of this is stuff might be related to the fact Managix just can't/won't handle a dynamic environment like AWS particularly well. 

> Managix issues encountered when creating a single node instance of AsterixDB on AWS
> -----------------------------------------------------------------------------------
>
>                 Key: ASTERIXDB-1082
>                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-1082
>             Project: Apache AsterixDB
>          Issue Type: Bug
>          Components: AsterixDB, Configuration
>            Reporter: Keren Ouaknine
>            Assignee: Ian Maxon
>
> A single node won't run on AWS.
> The failure I get is: 
> INFO: Substitute node joining : aws_single_catching_you_node1
> java.lang.NullPointerException
> 	at edu.uci.ics.asterix.hyracks.bootstrap.NCApplicationEntryPoint.updateOnNodeJoin(NCApplicationEntryPoint.java:250)
> 	at edu.uci.ics.asterix.hyracks.bootstrap.NCApplicationEntryPoint.start(NCApplicationEntryPoint.java:94)
> 	at edu.uci.ics.hyracks.control.nc.NodeControllerService.startApplication(NodeControllerService.java:318)
> 	at edu.uci.ics.hyracks.control.nc.NodeControllerService.start(NodeControllerService.java:255)
> 	at edu.uci.ics.hyracks.control.nc.NCDriver.main(NCDriver.java:44)
> Additionally a few issues require further investigation:
> 1. Why is Managix deleting the files under:
> /home/ec2-user/managix/clusters/local/working_dir/asterix
> It seems part of a cleanup process when an instance fail to be created, but it actually means you have to copy bin and repo (w all the jars files) under asterix manually before every instance creation attempt.
> 2. How come Managix is ALSO expecting to see bin and repo under a path containing the instance name. Ex:
> [ec2-user@ip-172-30-0-174 managix]$ managix create -n aws_single_catching_you -c $MANAGIX_HOME/clusters/local/local.xml
> ERROR: /home/ec2-user/managix/asterix/aws_single_catching_you/bin/asterixnc.bat (No such file or directory)
> 3. Why the call to transfer.sh misses the last parameter and thus need to be added manually??



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)