I'm on Origin 1.1.3
I've confgured the cluster-metrics (its in the openshift-infra project!). I'm 
able to see all the metrics (memory & cpu) on my metrics-tab.
Now I try to create a simple autoscaler:
oc autoscale dc/test --min 2 --max 15 --cpu-percent=70

I've edited the dc of my container so now it's using resources requests and 
limits.
In my webconsole I see the 2 cirkles and the MiB and millicores used.

But
oc get hpa
NAME      REFERENCE                     TARGET    CURRENT     MINPODS   MAXPODS 
  AGE
test      DeploymentConfig/test/scale   70%       <waiting>   2         15      
  21m

Target CPU utilization:        70%
Current CPU utilization:    <not available>

I read it was normal that the current state was waiting in the beginning. But 
it's already on <waiting> for 21 minutes. 
How can I check what's going wrong?

The logs of the pod where I've created the autoscaler doesn't show anything 
different than normal:
AH00558: httpd: Could not reliably determine the server's fully 
qualified domain name, using 10.1.1.14. Set the 'ServerName' directive 
globally to suppress this message

The logs of my metrics (but they seem to work fine):
casandra: INFO  12:59:51 Initializing hawkular_metrics.leases

heapster:
I0224 13:28:35.108008       1 manager.go:152] ScrapeMetrics: time: 107.715184ms 
size: 160
I0224 13:29:05.000203       1 manager.go:79] Scraping metrics start: 2016-02-24 
13:28:30 +0000 UTC, end: 2016-02-24 13:29:00 +0000 UTC
I0224 13:29:05.118256       1 manager.go:152] ScrapeMetrics: time: 117.97843ms 
size: 160
I0224 13:29:35.000209       1 manager.go:79] Scraping metrics start: 2016-02-24 
13:29:00 +0000 UTC, end: 2016-02-24 13:29:30 +0000 UTC
I0224 13:29:35.106305       1 manager.go:152] ScrapeMetrics: time: 106.009207ms 
size: 160
I0224 13:30:05.000266       1 manager.go:79] Scraping metrics start: 2016-02-24 
13:29:30 +0000 UTC, end: 2016-02-24 13:30:00 +0000 UTC
I0224 13:30:05.113913       1 manager.go:152] ScrapeMetrics: time: 113.477259ms 
size: 160

metrics deployer:
++ '[' -n '' ']'
Deploying the Heapster component
++ oc process hawkular-heapster -v 
IMAGE_PREFIX=docker.io/openshift/origin-,IMAGE_VERSION=latest,MASTER_URL=https://kubernetes.default.svc:443
++ oc create -f -
serviceaccount "heapster" created
service "heapster" created
replicationcontroller "heapster" created
+ echo 'Success!'
Success!

Hawkular-metrics:
12:59:48,619 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: 
Admin console listening on http://127.0.0.1:9990
12:59:48,620 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: 
WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final) started in 16058ms - 
Started 374 of 664 services (385 services are lazy, passive or on-demand)
12:59:52,446 INFO  
[org.hawkular.metrics.core.service.MetricsServiceImpl] 
(metricsservice-lifecycle-thread) HAWKMETRICS100001: Using a key space of 
'hawkular_metrics'
12:59:52,561
 INFO  [org.hawkular.metrics.api.jaxrs.MetricsServiceLifecycle] 
(metricsservice-lifecycle-thread) HAWKMETRICS200005: Metrics service 
started
                                          
_______________________________________________
users mailing list
[email protected]
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Reply via email to