Hi Adrian, thanks again Yes, I know - I tried tracking it down myself. I find the jClouds code a bit hard to comprehend.
BTW 50-1000 msecs are insanely small numbers IMO. No wonder AWS returned errors (Y) > On Nov 21, 2014, at 5:53 PM, Adrian Cole <[email protected]> wrote: > > sorry they are a bit indirect to track down! > > /** > * @see > org.jclouds.compute.config.ComputeServiceProperties#POLL_INITIAL_PERIOD > */ > public static final long DEFAULT_PERIOD = 50l; > /** > * @see org.jclouds.compute.config.ComputeServiceProperties#POLL_MAX_PERIOD > */ > public static final long DEFAULT_MAX_PERIOD = 1000l; > > > On Fri, Nov 21, 2014 at 6:02 AM, Yaron Rosenbaum > <[email protected]> wrote: >> Adrian, >> >> Thank you! >> BTW. What are the defaults? >> >> (Y) >> >>> On Nov 20, 2014, at 6:08 PM, Adrian Cole <[email protected]> wrote: >>> >>> Hi, Yaron. >>> >>> I believe you are looking to override these two from >>> ComputeServiceProperties. Use ContextBuilder.overrides (or set java >>> system properties) to do so! >>> >>> Hope this helps, >>> -A >>> >>> /** >>> * Initial period between the ComputeService's node polls. >>> Subsequent periods increase exponentially >>> * (based on the backoff factor) and become constant when the >>> maximum period is reached. >>> * The unit is milliseconds. >>> */ >>> public static final String POLL_INITIAL_PERIOD = >>> "jclouds.compute.poll-status.initial-period"; >>> >>> /** >>> * Once the exponentially increasing period between ComputeService's node >>> * polls has reached this maximum period, it remains at this value. >>> * The unit is milliseconds. >>> */ >>> public static final String POLL_MAX_PERIOD = >>> "jclouds.compute.poll-status.max-period"; >>> >>> >>> On Thu, Nov 20, 2014 at 12:42 AM, Yaron Rosenbaum >>> <[email protected]> wrote: >>>> Background: >>>> >>>> I am using jClouds to create and maintain a cluster. My cluster uses spot >>>> instances. >>>> >>>> As I understand it, jClouds is polling AWS to see whether the requested >>>> nodes have been created. >>>> This polling, however, happens too frequently for AWS - which blocks these >>>> requests returning an error. >>>> jClouds misinterprets this error as a failure to create, but leaves the >>>> spot request - which is eventually fulfilled. >>>> The created nodes are not configured by jClouds, and are left orphaned. >>>> >>>> In my case - this endlessly creates more and more nodes. >>>> ———————— >>>> >>>> 1) Is it possible to specify polling interval for new Spot instance >>>> requests ? How ? >>>> 2) Is it possible to ignore certain errors ? >>>> >>>> This is a blocker for me, so any help would be appreciated. >>>> >>>> >>>> (Y) >>>> >>
