Best unofficial Apache Server developers community
Username
Forgot password?
Sign in with Twitter account
Sign in with Facebook account
List archives

safe to use --replSet and --master at the same time?

large number of info messages: info DFM::findAll(): extent 0:2c00 was empty, skipping ahead
(35 lines)
Help! batchInsert on new sharded 1.6.1 cluster is now crawling!
(31 lines)
Aug 23, 2010
Dustin Norlander
Dustin Norlander
I am going to move towards using replica sets, but don't want to go
all at once.  Can I still use some regular slaves on a replica set
master?  Should I set --replSet and --master on the command line?





Reply
Tags: setsreplicacommand
Similar Threads
can a slave in replSet be a master of another replSet
I have 2 cdn. They are in different city.

replSet A in cdn A. I hope a slave in this replSet is in cdn B, and be
a master of another replSet which in cdn B.

So these 2 replSet have syn same data and service different city ,

Is that possible???





how to config master in replSet not for reading
In my service, read load in very heavy. I know slave in replSet can operate
for reading, then can I config master in replSet not operate for reading?

Is it possible?thanks





Re: Is it safe to replace master.db file?
OK thanks for the reply.  I have a partition and all my entries are under
that partition.  What I replaced was the master.db from in system folder
not
in my partition folder so will it affect?




Is it safe to replace master.db file?
Hi,

I am using ApacheDs 1.5.4, after running successfully for a long time, now
getting the following error:

Exception in thread "main" java.lang.NullPointerException
        at
org.apache.directory.server.core.entry.ClonedServerEntry.<init>
        (ClonedServerEntry.java:67)
        at

org.apache.directory.server.core.partition.impl.btree.jdbm.JdbmPartition.lookup
(JdbmPartition.java:457)
        at

org.apache.directory.server.core.partition.impl.btree.ServerEntryCursorAdaptor.get
(ServerEntryCursorAdaptor.java:140)
        at

org.apache.directory.server.core.partition.impl.btree.ServerEntryCursorAdaptor.get
(ServerEntryCursorAdaptor.java:40)
        at

org.apache.directory.server.core.filtering.BaseEntryFilteringCursor.next
(BaseEntryFilteringCursor.java:502)
        at org.apache.directory.server.core.authz.GroupCache.initialize
        (GroupCache.java:151)
        at org.apache.directory.server.core.authz.GroupCache.<init>
        (GroupCache.java:115)
        at

org.apache.directory.server.core.authz.AciAuthorizationInterceptor.init
(AciAuthorizationInterceptor.java:211)
        at

org.apache.directory.server.core.interceptor.InterceptorChain.register0
(InterceptorChain.java:439)
        at

org.apache.directory.server.core.interceptor.InterceptorChain.register
(InterceptorChain.java:395)
        at
        org.apache.directory.server.core.interceptor.InterceptorChain.init
        (InterceptorChain.java:255)
        at
       
org.apache.directory.server.core.DefaultDirectoryService.initialize
        (DefaultDirectoryService.java:1385)
        at
org.apache.directory.server.core.DefaultDirectoryService.startup
        (DefaultDirectoryService.java:840)
        at org.apache.directory.server.configuration.ApacheDS.startup
        (ApacheDS.java:126)
        at org.apache.directory.server.Service.init(Service.java:86)
        at org.apache.directory.server.UberjarMain.main
        (UberjarMain.java:56)



Problem starting HBase Master for the first time, EOFException
Dear hbase-users,

I was wondering if you might be able to help. I am trying to setup
HBase (and as such, Zookeeper) on Ubuntu 10.04 using the Cloudera
Karmic CDH3 distribution. Zookeeper has installed fine, however when
it comes to starting an hbase master, it falls over with the following
exception:

(stack trace summarised to last bit)
Caused by: java.io.EOFException
    at java.io.DataInputStream.readInt(DataInputStream.java:375)
    at
org.apache.hadoop.ipc.Client$Connection.receiveResponse(Client.java:508)
    at org.apache.hadoop.ipc.Client$Connection.run(Client.java:446)

Its clearly connecting to the HDFS, but it's giving it a strange
response. The section above of the trace identifies the hostname that
I've specified in the hbase.rootdir property in the hbase-site.xml and
also the IP address, which it must have looked up in DNS. For
information, that is set to:
hdfs://master:50071/hbase.

Also, as i'm just evaluating it at this stage, I'm installing
Zookeeper and hbase-master on the same machine as the namenode
(master). The regionservers will go somewhere else when I get to that
stage.

My hbase-site.xml was blank (between the configuration tags) and the
only things I've added so far are:

hbase.cluster.distributed="true"
hbase.rootdir="hdfs://master:50071/hbase"
hbase.zookeeper.quorum="master"

obviously in the <name><value> format of the XML file, without
the quotes.

I'm at a bit of a loss as to what is going on. I've tried a wget to
the namenode dfshealth.asp page and that works fine (obviously thats
http:// rather than hdfs://). Any pointers on where to look?

Many thanks,

Jamie

I ran a wget to


Problem with TTL and DLQ using Master/Slave failover on Master crash
Hi all,

 

we have set up a cluster of machines using ActiveMQ with Master/Slave
failover protocol. All messages use a TTL of 120 seconds and if TTL is
reached are sent to an individual DLQ.

Basically this works fine. However, there is one scenario where the
automatic routing of a message to the DLQ does not work:

 

-          a client receives message X but cannot commit the message
because of some error (e.g. network failure, hardware crash, etc.)

-          the ActiveMQ master crashes (clients now failover to the
slave)

-          message X reaches its TTL. This can be seen in the JMX
counters (EnqueueCount=1, DequeueCount=1, DispatchCount=0,
ExpiredCount=1)

-          message X is not routed to the DLQ as expected, the DLQ
remains empty

 

There are no warnings or error messages in the log files. Here is our
current broker and DLQ strategy configuration:

 

    <broker xmlns="http://activemq.apache.org/schema/core"
brokerName="localhost" persistent="true"
masterConnectorURI="tcp://queuemaster:61616"
shutdownOnMasterFailure="false">

 

       <policyEntry queue=">" producerFlowControl="true"
memoryLimit="1mb">       

              <deadLetterStrategy>

                     <individualDeadLetterStrategy queuePrefix="todo."
processNonPersistent="true" processExpired="true" />

              </deadLetterStrategy>

       </policyEntry>

 

 

Is there something that has to be addressed in the configuration to
support this scenario ?

 

 

Bye,

Daniel



Created: (HDFS-1307) Add start time, end time and total time taken for FSCK to FSCK report
Add start time, end time and total time taken for FSCK to FSCK report

ReplSet Secondary Lag
Hello,

How do I check the replication/sync status of a secondary replication
set member?

In other words, I would like the data available in
db.printSlaveReplicationInfo(), but for a replSet secondary member.

I started poking around local.oplog.rs but I'm not entirely sure how
to wield it.

Thanks,
Jerry





couldn't movePrimary in sharding+replSet?
In 1.6.1.

I need delete a shard which is a replSet. I use  { movePrimary:
"t_video_reference", to: "shard0001"  }, But return error. { "ok" : 0,
"errmsg" : "clone failed" }

db.printShardingStatus()

can I read slaves in replSet in version 1.6.1?
In 1.6.1.

I want to do some find operation in slave. But slave return

error: { "$err" : "not master", "code" : 10107 }

. I remember in 1.5.x, when I config db.getMongo().setSlaveOk() in master,
I
can read slave.

How to config this now??

In master,

 use admin
 db.getMongo().setSlaveOk()
 use t_video_reference                        # this is my database I
want
to find() sth.
 db.getMongo().setSlaveOk()

but In slave
I still couldn't find(). even "show collections".

My wrong understanding??

thanks.





replSet in Sharding must have a server in port 27018??
Firstly, I addShard "youku_imag/b05_mongodb.yoqoo:
27017,b06_mongodb.yoqoo:27017,b07_mongodb.yoqoo:27017"

the mongos log bellow:

Assertion: 13312:replSet error : logOp() but not primary
Hello together,

i'm experimenting on mongodb a while and since 1.6 i prepare the
productional use in our shop system.

While testing in a sharded environment with 3 shards, each a replica
set consisting of 2 mongod and one arbiter, i got following output on
two mongod processes (both secondary):

Fri Aug 13 09:46:09 [rs_sync] Assertion: 13312:replSet error : logOp()
but not primary?
0x80be341 0x8259956 0x8255156 0x82d1e60 0x834783a 0x8343597 0x834455c
0x8257722
0x824ba81 0x824dbfa 0x824ee3a 0x824ef58 0x824f350 0x80a4edf 0x8456c2d
0x8567f8a
0x85a6fbe
 [0x80be341]
 [0x8259956]
 [0x8255156]
 [0x82d1e60]
 [0x834783a]
 [0x8343597]
 [0x834455c]
 [0x8257722]
 [0x824ba81]
 [0x824dbfa]
 [0x824ee3a]
 [0x824ef58]
 [0x824f350]
 [0x80a4edf]
 [0x8456c2d]
 [0x8567f8a]
 [0x85a6fbe]

Is it something i should care about?
The MapReduce method i called when this occured is working as
intended.

Thank you in advance
Greetings from Germany
Maik





Jmeter time vs User Percieved time
Hi,

I am using Jmeter to stress the server with 50 concurrent users.At the
same
time I note down the manual time( i.e user perceived time as i am
interested
in the high level UI rendering time) by opening a browser and following
the
same steps as in Jmeter script. I am using three different machines for
this
( app server, Jmeter scripts & for browser). when I note the time
taken by
Jmeter for loading the jsp i am interested in it shows - average time =
19s
and 90% line = 35s, whereas the manual time for loading the same page is
7s.
I have used cache manager in Jmeter and also am using download all
embedded
resources so that jmeter can emulate the browser behaviour to some extent.
since Jmeter is not a browser and doesn't give the UI rendering time, I
expected the manual time to be more than the jmeter time not vice-versa.
(the times mentioned earlier are averages of multiple runs).
Now I am thinking should I even compare the two times? 



Incorrect response time - JMeter Response Time > Actual Response Time
Reproducible: Some time issue. 20% for each response time.
This is the issue for response time from jmeter.

I have record the request from site and run these request, but some of
response
time is larger than actual response time.

E.G. 
The request of http://www.x.com/note

Thread Name: Thread Group 1-1
Sample Start: 2010-07-27 08:46:50 PDT
Load time: 104555
Latency: 104555
Size in bytes: 239
Sample Count: 1
Error Count: 0
Response code: 200
Response message: OK

it shows 104sec for response time.
but actual for YSlow and Firebug, it's just 1 sec.
Also I have catch the time by manual with windows time.
It used 1 sec got the response time when running the scripts but it's show
104555 on Jmeter.

but this is not reproduce always and not only on designated request.
It has more than 20% in one round performance testing.
And it's randomly on each request.





Re: Safe way to backup an RDB file
Can an AOF file be backed up with a simple 'cp' command? Or must we
create a dump file to do a backup?

Thanks,
David

On Jul 27, 3:39 pm, Salvatore Sanfilippo <ant### @gmail.com> wrote:
 On Tue, Jul 27, 2010 at 9:31 AM, teleo <lev.### @gmail.com>
wrote:
 > What is the safest way to backup an RDB file in Redis?

 In Redis .rdb files can be copied while the server is running without
 any need of lock. No corruption is possible since the new file is
 always saved in a temp location and atomically rename(2)d to the new
 location.

 So just use "cp" :)

 Cheers,
 Salvatore

 > Thanks,
 > T

 > --
 > 
Do implementations of Watcher need to be thread-safe?
Hi,

Do implementations of Watcher need to be thread-safe, or can I assume
that process(...) will always be called by the same thread?

Thanks,
Josh "Ua" Ball


DO NOT REPLY SSI Servlet should support safe configuration
https://issues.apache.org/bugzilla/show_bug.cgi?id=48960

Mark Thomas <ma### @apache.org> changed:

           What    |Removed                     |Added

DO NOT REPLY SSI Servlet should support safe configuration
https://issues.apache.org/bugzilla/show_bug.cgi?id=48960

--- Comment #5 from Yair Lenga <yair.l### @citi.com> 2010-07-09
10:01:32 EDT ---
(In reply to comment #4)
 *** Bug 49520 has been marked as a duplicate of this bug. ***

Mark,

Is there anything I can do to speed up the inclusion of this change ? I've
noticed it did not make it for 6.0.28, where few other CGI/SSI related
changed
were incorporated. I would love to use the SSI, but I can not use it
because of
the security reisk of the "unsafe" include/exec.




DO NOT REPLY SSI Servlet should support safe configuration
https://issues.apache.org/bugzilla/show_bug.cgi?id=48960

--- Comment #8 from Mark Thomas <mar### @apache.org> 2010-07-13
17:16:40 EDT ---
The diff is inverted and the patch is using tabs rather than spaces. I
should
eb able to work with that but you might need to fix it.




DO NOT REPLY New: SSI Servlet should support safe configuration
https://issues.apache.org/bugzilla/show_bug.cgi?id=49520

           Summary: SSI Servlet should support safe configuration
           Product: Tomcat 7
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: major
          Priority: P2
         Component: Catalina
        AssignedTo: de### @tomcat.apache.org
        ReportedBy: yair.### @citi.com


This is a duplicate request from the Tomcat 6 (Bug 48960). See proposed
solution/discussion:
https://issues.apache.org/bugzilla/show_bug.cgi?id=48960

The current configuration of the SSI module is "All" or "None". The "ALL"
option will expose all the legacy Apache SSI directive (echo, printenv,
if,
exec, ...). As documented, allowing SSI will allow execution of arbitrary
programs using the "exec". As a result, there is no safe way to expose
sites/projects containing SSI directive, without taking a security risk,
or
reviewing of every file.

The "exec" directive, with the cmd option is a major risk. Even for
Apache, you
have the option to allowing the "safe" include (includeNoExec). The
includeNoExec allow pages to be served, even when the content is not
reviewed,
or when users are allowed to upload content to the site.

I have a big site which need to be converted into JSP. I would like to use
the
SSI servlet to allow for transition over time. The extra risk from ( from
exec
cmd) make it impossible to deploy the SSI.

My request: Modify the configuration of SSI as follow: By default, it will
only
allow "safe" directive (no exec cmd=...). This will eliminate the risk
from
arbitrary execution of commands ("del *.*"). It will also remove many
potentail
load problems. The cmd= should only be allowed using a directive like
"allowUnsafeExec", which will default to false.

I think that the change will make it easier to use the SSI feature,
without
exposing the server to big risk. The risk associated with the "safer"
version
of SSI is similar to the risk from running JSP pages.

A better alternative is to eliminate the "exec cmd=" option alltogether.