I just upgraded to 2.14 and it fails to initialize now. It was working
ok with 2.13:

ERROR 2011-10-03 11:58:30,221 Membase.MembasePool - Failed to
initialize the pool.
System.FormatException: An invalid IP address was specified.
at System.Net.IPAddress.InternalParse(String ipString, Boolean
tryParse)
at System.Net.IPAddress.Parse(String ipString)
at Membase.MembasePool.InitVBucket(ClusterConfig config,
ISaslAuthenticationProvider auth)
at Membase.MembasePool.ReconfigurePool(ClusterConfig config)

I am using manual configuration.

memcacheConfig.Bucket = farmName;
memcacheConfig.NodeLocator =
typeof(DefaultNodeLocator);
memcacheConfig.KeyTransformer = new
TigerHashKeyTransformer();
memcacheConfig.Transcoder = new DefaultTranscoder();

XmlNodeList servers =
farmStgs["servers"].SelectNodes("add");
foreach (XmlNode svr in servers)
{
memcacheConfig.Urls.Add(new
Uri(svr.Attributes["uri"].Value));
}

This is my server config:

<Membase raiseErrors="false" logErrors="true">
<servers>
<add uri="http://d0002cache01:8091/pools/default" />
</servers>
<socketPool minPoolSize="3" maxPoolSize="10" connectionTimeout="3"
deadTimeout="120" receiveTimeout="3" />
</Membase>

and here is what comes back from my pool url:

{
"storageTotals": {
"ram": {
"quotaUsed": 2147483648,
"usedByData": 457186635,
"total": 4140843008,
"quotaTotal": 3312451584,
"used": 4077023232
},
"hdd": {
"usedByData": 1729655848,
"total": 11408424960,
"quotaTotal": 11408424960,
"used": 4905622732,
"free": 6502802228
}
},
"name": "default",
"alerts": [],
"nodes": [
{
"systemStats": {
"cpu_utilization_rate": 6.030150753768845,
"swap_total": 4194295808,
"swap_used": 0
},
"interestingStats": {
"curr_items": 258121,
"curr_items_tot": 258121,
"vb_replica_curr_items": 0
},
"uptime": "350929",
"memoryTotal": 4140843008,
"memoryFree": 63819776,
"mcdMemoryReserved": 3159,
"mcdMemoryAllocated": 3159,
"clusterMembership": "active",
"status": "healthy",
"hostname": "d0002cache01:8091",
"clusterCompatibility": 1,
"version": "1.7.1.1",
"os": "x86_64-unknown-linux-gnu",
"ports": {
"proxy": 11211,
"direct": 11210
}
}
],
"buckets": {
"uri": "/pools/default/buckets?v=88509917"
},
"controllers": {
"addNode": {
"uri": "/controller/addNode"
},
"rebalance": {
"uri": "/controller/rebalance"
},
"failOver": {
"uri": "/controller/failOver"
},
"reAddNode": {
"uri": "/controller/reAddNode"
},
"ejectNode": {
"uri": "/controller/ejectNode"
},
"testWorkload": {
"uri": "/pools/default/controller/testWorkload"
}
},
"balanced": true,
"failoverWarnings": [],
"rebalanceStatus": "none",
"rebalanceProgressUri": "/pools/default/rebalanceProgress",
"stopRebalanceUri": "/controller/stopRebalance",
"nodeStatusesUri": "/nodeStatuses",
"stats": {
"uri": "/pools/default/stats"
}
}

Search Discussions

  • Michael Delaney at Oct 10, 2011 at 10:40 pm
    i'm getting the same error on a cluster on 2 nodes on ec2.

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupenyim-memcached @
categoriesmemcached
postedOct 3, '11 at 4:15p
activeOct 10, '11 at 10:40p
posts2
users2
websitememcached.org

2 users in discussion

Bradrover: 1 post Michael Delaney: 1 post

People

Translate

site design / logo © 2021 Grokbase