Skip to content
This repository has been archived by the owner on Sep 13, 2022. It is now read-only.

Bootstrap registry fails to come up #38

Open
rafajeng opened this issue Jan 27, 2019 · 1 comment
Open

Bootstrap registry fails to come up #38

rafajeng opened this issue Jan 27, 2019 · 1 comment

Comments

@rafajeng
Copy link

rafajeng commented Jan 27, 2019

Hi, Quobyte team.

I'm evaluating quobyte on k8s for the first time. After apply services.yaml, the bootstrap registry fails to come up with following errors:

Picked up _JAVA_OPTIONS: -XX:+RelaxAccessControlCheck -XX:+UseThreadPriorities -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/var/crash -XX:+UseG1GC -XX:MaxGCPauseMillis=25 -XX:+ExplicitGCInvokesConcurrent -Dfile.encoding=UTF-8 -Dsun.jnu.encoding=UTF-8 -Xmx512m -Xms64m -XX:MaxDirectMemorySize=1G -Djava.library.path="/opt/quobyte/lib/"

OpenJDK 64-Bit Server VM warning: If the number of processors is expected to increase from one, then you should configure the number of parallel GC threads appropriately using -XX:ParallelGCThreads=N

[ I | REGISTRY | 1 | Jan 27 14:17:30.781 ] Maximum usable memory: 512M
[ I | REGISTRY | 1 | Jan 27 14:17:30.792 ] Service configuration file ./host.cfg does not exist.
[ I | REGISTRY | 1 | Jan 27 14:17:30.792 ] Service configuration file /root/.quobyte/host.cfg does not exist.
[ I | REGISTRY | 1 | Jan 27 14:17:30.794 ] Loaded service configuration from /etc/quobyte/host.cfg
[ I | REGISTRY | 1 | Jan 27 14:17:30.796 ] Loaded service configuration from /etc/quobyte/registry.cfg.
[ I | REGISTRY | 1 | Jan 27 14:17:30.805 ] This service has uuid 93f1a678-5325-4f65-88c3-b44de7a8eeca and uses directory service registry
[ I | REGISTRY | 1 | Jan 27 14:17:30.884 ] Quobyte Registry Service version 2.11.2 (6586165)
[ I | TSync Thr | 10 | Jan 27 14:17:30.884 ] TimeSync is running using the local clock
[ I | REGISTRY | 1 | Jan 27 14:17:30.886 ] Monitoring devices via /proc/mounts
[ I | REGISTRY | 1 | Jan 27 14:17:30.886 ] Monitoring devices in /var/lib/quobyte/devices/

SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.

[ I | REGISTRY | 1 | Jan 27 14:17:31.093 ] Configured registry target(s): [registry]
[ I | REGISTRY | 1 | Jan 27 14:17:31.093 ] Registry target 'registry' consists of a single DNS record or IP address. Attempting to resolve it as an SRV record, an A record with multiple targets and default ports, or a host name/IP address with default port.
`

Is there some new change in 2.11.2 that causes this issue?

Please help

Thanks

@quolix
Copy link
Contributor

quolix commented Jan 28, 2019

Hi Rafael,

it says: "Registry target 'registry' consists of a single DNS record or IP address. Attempting to resolve it as an SRV record, an A record with multiple targets and default ports, or a host name/IP address with default port.

It tries to resolve the DNS name 'registry', but can't. Have you set up k8s DNS so that it resolves from within any pod to the IPs of the registry daemon set?

You could also use the operator to deploy Quobyte:
https://github.com/quobyte/k8s-operator

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants